-
Suggestion
-
Resolution: Low Engagement
-
None
-
3
-
I first wasn't sure if this was a bug or missing feature, Support confirmed it was the latter (see JSP-191903).
Support suggested that I create the feature request in the Stash project; please move to JIRA if it rather belongs there.
So I have a repo in Stash with the feature branching stuff turned on and configured, and I have set up JIRA integration.
After creating my first issue for a bug, I used the "Create feature branch" link in JIRA's Development Panel to start development on it. I saw the branch was already named with the issue key and summary (e.g. "bugfix/IDC-2-issue-summary-goes-here"), so I committed all my stuff in there without mentioning the issue key again in the commit messages, expecting them to still show up in JIRA's Source Tab because the branch had the issue key in its name – I thought JIRA was "smart" enough to also catch them because of that, which it obviously does not.
Wouldn't it make more sense to treat any commit in such feature branches relevant? Because I think there aren't that many cases in which you'd commit code into a specialized feature branch dedicated to one single JIRA issue that has nothing to do with that feature/linked issue at all. And since programmers are generally lazy, why (remember to!) type the issue key into every single commit message when it's already there, sitting in the branch name where JIRA/Stash could theoretically find it too?
I of course understand that, with a very basic branching scheme where everyone directly commits their stuff to `master`, you'd of course need the key directly in commit messages – but when using `git-flow` and the like (like me in this case here) it really doesn't make any sense at all.
After all it also would add some consistency, given JIRA's "Create feature branch" feature which already prepopulates the branch name field in the form with the issue key per default as well as Stash's specific support for feature branching. Those were the two major points that caused my confusion here leading to the support request - I simply expected JIRA/Stash to work like that because these two features were there.
- relates to
-
- Closed
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-4669] Show any commits inside a properly named feature branch in that issue's development panel
No plans at present, aldanor. It's something we'd like to do, but it's not high on the list at the moment.
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bitbucket Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues.
Kind regards,
Bitbucket Data Center