Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-3967

Custom Branch Types/Prefixes



    • 114
    • 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 Jan 2022

      Hi everyone,

      Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Data Center.

      We spend a significant amount of time determining our product investments in Bitbucket Data Center. Unfortunately, we are not planning to address this suggestion in the next 12 months. In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request description templates, capability to enable/disable source branch deletion on merging pull requests and our upcoming roadmap includes a number of other top voted suggestions, including repository archiving. Please check out our public roadmap for more details on the coming soon and future items.

      I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.


      Anton Genkin
      Product Manager - Bitbucket Data Center & Server

      Original suggestion
      Our team is thoroughly enjoying the new branching features in Stash 2.8 along with the JIRA 6.1 integration, but there is one little issue...

      We follow a Github-style feature-branch workflow, where master is considered "production-ready", and all changes are handled in branches that are eventually merged back in. The issue we're having is that while "bugfix" and "feature" work for many instances, and "custom" handles the rest, we'd like to enforce project-specific branch types (For example "client/" for billable client customizations...)

      Would be nice if there was a way to define custom types/prefixes in the repo settings, and have them show up under "Branch Type" when creating a new branch.


        Issue Links



              Unassigned Unassigned
              b57cc4ce9c52 Josh Kritner
              203 Vote for this issue
              103 Start watching this issue