-
Suggestion
-
Resolution: Unresolved
-
None
-
26
-
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.
Meantime, we recommend having a look at Create Branch Wizard for Bitbucket from Atlassian Marketplace. Our ecosystem is an important aspect of the product, providing flexibility where people want different or additional functionality, and maintaining simplicity where they don't.
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 description
What is needed is an option to customise how branch names are set by default, originally their are composed by the issue key and summary of the issue in JIRA, although what we want is to customise it to set only the issue key without any summary or additional data.
As an example:
How it is now: branch name: JSP-3745-research-for-issues-on-jira
How we want: JSP-3745
We are able to change the branch name when creating it, although we want a global configuration that we won't have to change it every time.
- duplicates
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Add option to adjust the auto-fill values for branch names in BitBucket
-
-
Resolution: Unresolved
-
None
-
26
-
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.
Meantime, we recommend having a look at Create Branch Wizard for Bitbucket from Atlassian Marketplace. Our ecosystem is an important aspect of the product, providing flexibility where people want different or additional functionality, and maintaining simplicity where they don't.
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 description
What is needed is an option to customise how branch names are set by default, originally their are composed by the issue key and summary of the issue in JIRA, although what we want is to customise it to set only the issue key without any summary or additional data.
As an example:
How it is now: branch name: JSP-3745-research-for-issues-on-jira
How we want: JSP-3745
We are able to change the branch name when creating it, although we want a global configuration that we won't have to change it every time.
- duplicates
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Gathering Interest
- mentioned in
-
-
-
-
-
-
-
-
Unassigned
-
Paulo Miguel (Inactive)
- Votes:
-
209 Vote for this issue
- Watchers:
-
108 Start watching this issue
- Created:
- Updated: