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

Settings for mapping (custom) issue types to branch model types for create branch

    • 42
    • 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 November 2023

      Hi everyone,

      Thank you for your feedback. We appreciate your input and understand the importance of addressing our users' suggestions. Unfortunately, we don't have plans to address this specific suggestion in the next 12 months.

      However, I want to assure you that your feedback is valuable to us. Over the last 12 months we have successfully implemented many highly voted suggestions including code-owners, resolvable comments and auto-merge and our upcoming roadmap includes a number of other top voted suggestions including dark theme, draft pull requests and multi-line comments. For the most up-to-date information on what features are coming soon please visit our roadmap.

      Once again, thank you for sharing your thoughts with us. Your feedback plays a crucial role in shaping the future of our product. We do continually review these priorities and will continue to do so over the coming year to determine when and how we might be able to address this idea. You can learn more about our prioritization process here.

      Cheers,

      Sarah Bolt

      Product Manager - Bitbucket Data Center

       Original suggestion

      The Subject should tell you all about my issue. We have some custom issue types and we would like to map them to the branching model. We love the Create Branch Link in the Jira Issue but currently we have to select the correct branch type

            [BSERV-4139] Settings for mapping (custom) issue types to branch model types for create branch

            You could use our app Create Branch Wizard for Bitbucket to achieve this, which now also supports Bitbucket Data Center.
            It allows mappings between Jira issue types and branch model types.

            Besides that, you can even fully customize your branch names with a template and variables.

            Some examples:

            • Branch created from issue type story:      $component/$fixVersion/$issueKey e.g. frontend/1.0/MYPROJ-1
            • Branch created from issue type subtask: $component/$fixVersion/$parentIssueKey_$issueKey e.g. frontend/1.0/MYPROJ-11_MYPROJ-1

            Depending on the Jira issue type, you can also configure which branch values should be filled in. E.g., for a hotfix Jira issue type, use "main" as a "Branch from" value.

            If you have any questions, check our documentation for more information or schedule a live demo.

            Michael Rüegg [Mibex Software] added a comment - You could use our app Create Branch Wizard for Bitbucket to achieve this, which now also supports Bitbucket Data Center . It allows mappings between Jira issue types and branch model types. Besides that, you can even fully customize your branch names with a template and variables. Some examples: Branch created from issue type story:      $component/$fixVersion/$issueKey e.g. frontend/1.0/MYPROJ-1 Branch created from issue type subtask: $component/$fixVersion/$parentIssueKey_$issueKey e.g. frontend/1.0/MYPROJ-11_MYPROJ-1 Depending on the Jira issue type, you can also configure which branch values should be filled in. E.g., for a hotfix Jira issue type, use "main" as a "Branch from" value. If you have any questions, check our documentation for more information or schedule a live demo .

            Hey look! This issue turns 8 years old today!

            Andrej Marinic added a comment - Hey look! This issue turns 8 years old today!

            Hey look! This issue turns seven years old today!

            Please can we get an update in celebration? This would be a really useful feature and hasn't had an update in four years.

            Rick Measham added a comment - Hey look! This issue turns seven years old today! Please can we get an update in celebration? This would be a really useful feature and hasn't had an update in four years.

            filipson added a comment -

            This would really help me and my team to work properly

            filipson added a comment - This would really help me and my team to work properly

            I would appreciate if it is possible to configure the source branch and branch type

            Marco Graf added a comment - I would appreciate if it is possible to configure the source branch and branch type

            Hi,

            We have an app called Create Branch Wizard in the Marketplace that, besides automatically selecting the right repository in the create branch dialog based on scanning Jira issue keys in the commit messages of the repository, can also be configured to map Jira issue types to Bitbucket branch types.

            Best regards,
            Michael from Mibex Software

            Michael Rüegg [Mibex Software] added a comment - Hi, We have an app called  Create Branch Wizard in the Marketplace that, besides automatically selecting the right repository in the create branch dialog based on scanning Jira issue keys in the commit messages of the repository, can also be configured to map Jira issue types to Bitbucket branch types. Best regards, Michael from Mibex Software

            I'd like to be able to set the default branch type when creating a branch in a specific Jira issue type. Right now, developers have to manually perform the action which leads to human error and inconsistency. 

            schow-lmi3d added a comment - I'd like to be able to set the default branch type when creating a branch in a specific Jira issue type. Right now, developers have to manually perform the action which leads to human error and inconsistency. 

            In my company a Bug is called something else but we still use the bugfix/ prefix. Please add the ability to map JIRA types to namespaces so I don't have to write and enforce another developer guideline.

            andrewjpreston added a comment - In my company a Bug is called something else but we still use the bugfix/ prefix. Please add the ability to map JIRA types to namespaces so I don't have to write and enforce another developer guideline.

            I have some of our users which would be very happy for such a solution, to map issue types to branch types!

            Martin, SCM Support added a comment - I have some of our users which would be very happy for such a solution, to map issue types to branch types!

            Brent P added a comment -

            borga910991060 - Unfortunately, there's not a good way to match JIRA issue types except by name. But I think it's reasonable to expect that Bitbucket Server can deal with the default issue type names for the 4 supported languages (English, German, French and Japanese). I've created a bug to fix that: BSERV-9012

            Brent P added a comment - borga910991060 - Unfortunately, there's not a good way to match JIRA issue types except by name. But I think it's reasonable to expect that Bitbucket Server can deal with the default issue type names for the 4 supported languages (English, German, French and Japanese). I've created a bug to fix that: BSERV-9012

              Unassigned Unassigned
              591677115db2 LarsM
              Votes:
              172 Vote for this issue
              Watchers:
              110 Start watching this issue

                Created:
                Updated: