-
Suggestion
-
Resolution: Unresolved
-
None
-
29
-
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
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.
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
[BSERV-3967] Custom Branch Types/Prefixes
You could use our app Create Branch Wizard for Bitbucket to achieve this, which also supports Bitbucket Data Center.
You can add your own branch types by fully customizing the branch names with templates and variables.
Some examples:
- Branch created from issue type story: client/$component/$fixVersion/$issueKey e.g. client/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.
+1, even just have task/my-branch would help. Sometimes its not a bug or a feature.
I'd like to see this too. +1 (Use case, map sub-tasks to chore/... branches) ...
+1
Our users sometimes forget to type in our desired prefix when they press the Custom button. If I could add that prefix to the pull-down, it would help a ton!