Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-3586

Allow user to select branch by typing exact branch name

XMLWordPrintable

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

       

      Atlassian status as of July 2020

      Hi everyone,

      From Bitbucket Server and Data Center 7.2 we prioritize the exact branch name matches.

      When searching for a branch by its name, you will now see it first in the list of results if it matches the exact name or prefix you typed in. No more scrolling through an alphabetized list of branch results that contain the text.

      Cheers,
      Imran Khan
      Product Manager - Bitbucket Server

      Original description:

      It would be very convenient if Stash would allow users to select branches by typing their exact name (for example, "master"). Currently, Stash just brings up a list of all branches that contain the typed text and one must scroll through the list to choose the right one.

      We have a fairly large repository, and a large number of branches contain the word 'master'. This requires scrolling down through pages of imperfect matches until reaching the true "master" branch. It's even trickier due to the fact that the branches don't appear to be sorted in alphabetical order by letter.

      Would it be possible to modify the branch selection in Stash so a user could simply type a branch name like 'master'. hit enter, and have stash select the exact match (if one exists?)

        1. release1.png
          40 kB
          Mark Lassau
        2. release2.png
          63 kB
          Mark Lassau
        3. release3.png
          50 kB
          Mark Lassau

            Unassigned Unassigned
            805e535774f3 Cameron Lewis
            Votes:
            10 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: