Extend pull request text search to include branch names

Question

Currently, the pull request search bar in the Bitbucket UI only matches text from the title and description of a PR. This means if a user searches for a branch name (e.g., hotfix/NOX-986), the PR is not found unless the branch name is manually included in the PR title or description.

Requested Enhancement:

* Include source branch name and destination branch name in the scope of the pull request text search.

* This way, searching for feature/abc-123 or hotfix/xyz directly finds the relevant pull request, even if the branch name is not mentioned in the PR title/description.

Benefits:

* Makes it easier and faster to locate PRs by their branch.

* Reduces reliance on teams manually adding branch names into PR titles.

* Improves developer workflow in repositories with many active branches and PRs.

Theodora Boudale · Answer

Hi Sahil,

Thank you for the feedback.

I went ahead and create a feature request in our public issue tracker:

* https://jira.atlassian.com/browse/BCLOUD-23849

Please make sure you add your vote to that feature request (by selecting the link Vote for this issue) to increase the chances of this being implemented. You are more than welcome to leave feedback, and you can also add yourself as a watcher (by selecting the link Start watching this issue) if you'd like to be notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

sahil trambadiya · Answer

Thanks for the suggestion! I’ll raise it in the Product Ideas portal so the team can consider it. This feature would definitely make searching PRs much easier.

sahil trambadiya · Answer

Hi Theodora,

Thanks for your quick response.

I need this feature mainly on the repo pull request page. It would be even better if it could also be implemented on the workspace pull request page.

Regarding the filter options:

Yes, there is a target branch filter, but no source branch filter.

Adding a source branch filter could help, but it still has limitations because once a branch is deleted after the PR is approved, it won’t appear in the filter anymore (this is the same issue with the target branch filter as well).

That’s why extending the PR text search to also include source and target branch names would be ideal. It allows us to quickly find PRs by branch name directly in the search box without worrying about deleted branches or missing filter options.

Kind regards,
Sahil