When you use pipeline multibranch you get all the branches for your project (or whatever filter you have) in one job page in a list view.

Some branches may have special meaning, or value that you may want grouped together (e.g. master stable develop etc) and not mixed in with other branches (PRs, random issue fixes etc etc.)

Therefore it would be really useful if you could assign some "weight" to some branch names (via a regexp or something) that you could use for ordering so that your "important to most people" branches are easier to find by always being at the top of the page before less important noise branches like (fixes, PRs), when viewed in the list view.

You can somewhat do this with a naming policy but if you already have a policy for "master" and "production" "test" branches then the PRs get mixed in between these forcing you to change you branching name policy which may be rippled through the organisation and existing tooling.