Branches with PR not showing PR in branches page

On Bitbucket Cloud, we search for all feature branches on the Branch View page and look for branches without a PR. We had two branches with open PR's to merge into another feature branch. Unfortunately these branches show on this page that they have no PR.

This is easy to recreate. Create branch 1 with PR to merge into develop. Create branch 2 with PR to merge into branch 1. Look at branches page. It will show PR only for branch 1.

This is just the basic branches page and the URL is like this:
https://bitbucket.org/companyname/repositoryname/branches/?search=feature

We initially submitted this to Bitbucket Cloud Support and Atlassian responded that the design of the Branch View page is to only show Pull Requests to merge into the main branch. In our opinion, this is not an acceptable resolution. If we set the main branch to anything but develop then it will display all of the other feature branches as not having a PR. Why would we only want to see branches without a PR to develop? The page says branches without a PR but that's not what it is. Instead it is "branches without a PR directly to the main branch" which is not particularly useful. Why would anyone want to tacitly ignore PRs merging to non-default branches?

Atlassian suggested that we post this here "to allow our developers who would be in a better position to advise on this matter as well as for you to engage in a discussion and forward your opinions and thoughts."