Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
87
-
Description
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.
Attachments
Issue Links
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
