Branch search on Create Pull Request should handle exact matches

4 votes

Our main branch name is dev

Our feature branch names are of the form ISC-xxxx\dev, where ISC-xxxx is the Jira ticket number
When I create a PR, I want the PR to go to dev, but if I type dev in branch dropdown for search, dev appears after a large number of other branches
ISC-123/dev
ISC-456/dev
[snip]
dev

If I press enter after trying dev, it picks the first result in the search.
This means I have to scroll down to find the actual dev branch

I think the search should
Look for an exact match, and put that first
Look for any branches that start with your search term, put those next
Finally include any branches that include but don't start with your search term.

Under consideration Quality of Life Suggested by: Bela VanderVoort (20 Jul, '21) • Upvoted: 28 Oct, '22 • Comments: 1

Comments: 1

28 Oct, '22
Bela VanderVoort
I know this probably isn't high priority, but the problem has been slowly becoming more annoying as our team grows and we have old branches that hang around.

This is how much scrolling I currently have to do.
https://www.screencast.com/t/MFYgCgllb6m

It seems like it is theoretically something that should be somewhat straightforward to fix.