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

Custom Branch Types/Prefixes

    XMLWordPrintable

    Details

    • UIS:
      111
    • Feedback Policy:
      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.

      Description

      Atlassian status as of December 2016

      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 Server.

      We spend a significant amount of time on an ongoing basis to determine our product investments in Bitbucket Server. Unfortunately, we are not currently planning to address this suggestion in the next 12 months. In the last 12 months, we've resolved 10 of the top 30 feature requests, and our upcoming roadmap includes a number of other top voted suggestions, including in-browser editing, improvements to search functionality, better JIRA integration, and providing an even better code review experience.

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

      Norman Ma

      Product Manager - Bitbucket Server

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              solsys Josh Kritner
              Votes:
              148 Vote for this issue
              Watchers:
              87 Start watching this issue

                Dates

                Created:
                Updated: