-
Suggestion
-
Resolution: Unresolved
-
None
-
4
-
10
-
Hi everyone,
Thanks for providing your thoughts and votes on this suggestion. We know it's been a while since this suggestion was raised and we're sorry to have kept you so long without a clear answer.
Your feedback has really helped us better understand the varied challenges you face with inability to see branch information in the list of commits in the development panel. Despite our lack of communication, this problem is actually one of those areas we plan to improve in Jira. Right now we've decided to prioritise it on our roadmap.
Thank you again for all your feedback on this suggestion and we look forward to providing you with more updates as we work on improving user experience of the Development panel.
Best,
Anton Genkin | Product Manager - Integrations
This was requested to be entered as an improvement per https://confluence.atlassian.com/display/JIRA/Viewing+the+Code+Development+Information+for+an+Issue?focusedCommentId=457704004#comment-457704004
After conversion to the new Development panel with upgrade to Jira 6.2, the Commits tab no longer shows (since we are connected to GitHub, which is expected). The old Commits tab, however, listed the branch name in the commit detail view. The new Development tab does not list the branch name along with the commit in the commits detail overlay. This was extremely valuable information, since not all of our branches follow the "feature branch" format (for example our "prerelease" and "bugpatch" branches). For those branches that are not tagged with the issue number, we now can no longer tell which branch the commits have been pushed to, since that information does not show up anywhere in the Development panel. As a side note, our QA department used the Commits tab in this manner: Click on it in one issue, go through the list of open stories for testing to see which branches things were on. Because the "last selected" tab was automatically selected when opening another issue, that allowed QA to flip through the issues with minimal interaction. That is now also not possible with the Development panel, as you must click on the commits link in every issue in order to view the information.
A configurable flag to also show the Commits tab would be an acceptable improvement, but showing the branch identifier in the Commits detail list is really a better improvement (although more clicks, we have other ways to flip through the list)
JIRA Version v 6.1.7
JIRA Version v 7.1.2
- duplicates
-
- Closed
- is related to
-
- Closed
-
FUSE-986 Failed to load
- links to
[JSWSERVER-14934] Branch information missing from the list of commits in the Development panel
Dear Atlassian team, this is a critical function for DEV and QA teams. It would be nice to have the branch info in Bitbucket. Please add this.
+100500 to higher the priority.
Dear Atlassian, any news on this issue? Are there any architectural difficulties with the implementation, or the task is still low priority?
For our company, this is the most critical lack of functionality in Bitbucket.
I look forward to checking out your source code (when/if you release it)!
The key people have probably been at Atlassian Summit this week: https://www.atlassian.com/summit/sessions/schedule?tab=monday%2C-october-10
I suspect support will get back to normal starting next week.
We solved it by writing our own translator between Github webhook payload and SCM Activity For Jira using sparkJava for web, Gson for json serialization and Jersey for REST push to the jira plugin's api.
here's our tool to catch github enterprise or github.com webhook payloads and replicate them to SCM Activity For Jira
https://github.com/attivio/scmsynchronizer
We make the changeId "<git-short-id> - <branchName>" or merge's between branches get blocked.
I doubt Atlassian will address this probably anytime soon as support went dark on us two or three days ago with no response to repeated attempts to contact them. Atlassian's legendary support seems exactly rather mythical at present.
I believe Atlassian's model for determining feature importance is somewhat flawed. If the majority of server installations turn off the usability data capture/phone-home feature then the set skews towards the SAAS offering which is perhaps why branch is included for Bitbucket but not other git servers.
Peter Kahn
added a comment - - edited We solved it by writing our own translator between Github webhook payload and SCM Activity For Jira using sparkJava for web, Gson for json serialization and Jersey for REST push to the jira plugin's api.
here's our tool to catch github enterprise or github.com webhook payloads and replicate them to SCM Activity For Jira
https://github.com/attivio/scmsynchronizer
We make the changeId "<git-short-id> - <branchName>" or merge's between branches get blocked.
I doubt Atlassian will address this probably anytime soon as support went dark on us two or three days ago with no response to repeated attempts to contact them. Atlassian's legendary support seems exactly rather mythical at present.
I believe Atlassian's model for determining feature importance is somewhat flawed. If the majority of server installations turn off the usability data capture/phone-home feature then the set skews towards the SAAS offering which is perhaps why branch is included for Bitbucket but not other git servers. I wrote a JIRA add-on to help solve this. Requires that your company is already using Bitbucket Server (aka Stash).
Marketplace link: Git Graph for JIRA
Add-on documentation here: Git Graph for JIRA Documentation
Peter Kahn
added a comment - We may need to find another suite due to this lack of critical functionality. I don't understand why it was removed when it worked in 5.x
Peter Kahn
added a comment - We may need to find another suite due to this lack of critical functionality. I don't understand why it was removed when it worked in 5.x Even pull requests in the development panel don't say which branch they are merging into. 
Nobody really cares that there's a commit with TKT-101 in some random branch in a git repo. They care that said commit is on its way into a release, and branch information is the only way to know!
I just upgraded to Jira 7 and was really looking forward to the development panel, but it's worse than useless: it just confuses my test team!
Yaniv Sayeh
added a comment - Luke, most repos don't follow 100% of git-flow.
What's up with this issue? It will be great to have this field.
Yaniv Sayeh
added a comment - Luke, most repos don't follow 100% of git-flow.
What's up with this issue? It will be great to have this field. 
Luke Rajlich
added a comment - The feature, as is, is not that useful for git flow. Single issue branches & PRs? Epics? Ok, those work, but most teams don't a PR workflow against single issue branches (we don't) and epics cover only a relatively small subset of development workflows.
What we'd like to be able to do is to track issues and associated commits through the QA process: feature branch -> develop -> staging -> master (production). Unfortunately, it's not visible right now in JIRA and we have to separately track this progress.
Luke Rajlich
added a comment - The feature, as is, is not that useful for git flow. Single issue branches & PRs? Epics? Ok, those work, but most teams don't a PR workflow against single issue branches (we don't) and epics cover only a relatively small subset of development workflows.
What we'd like to be able to do is to track issues and associated commits through the QA process: feature branch -> develop -> staging -> master (production). Unfortunately, it's not visible right now in JIRA and we have to separately track this progress. 
Dears, we are a middle-grade FinTech IT company and we are constantly working with 3 parallel branches. This feature is paramount for us - it's very uncomfortable to work with commits in Jira when one can't see the branch infotmation for each commit.