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.

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.

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

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!

Luke, most repos don't follow 100% of git-flow.

What's up with this issue? It will be great to have this field.

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.

Any news on that?
It would be great to have the branch info, right now if you commit a change against multiple branches you just see the list of the same file.
Our Test team would need access to the repo to see the actual branches...

Our Testers and Release Manager have been making the same comments. Having the ability to see, at a glance, which Branch a given commit originated from, and a status of that Branch (e.g. is it still open, was it merged with default since the commit, is it closed?) would greatly help them to understand the lifecycle of a commit and the state of default/mainline without having to refer to developers. (Pilfered from my description in DCON-404).

I also recommend increasing the priority on this, it's crucial to see this data with minimal clicking. Right now we can't see branch information at all in issue view.

We'd prefer the option to set a flag to restore the commit tab as it was please.

Our QA team also needs this information.
And it was very comfortable to use when it was placed as separate tab at the activity section (near comments, history etc).
+1 to higher the priority.

Even we as developers use this functionality often to get easily an overview what commits are there across all branches we have. We miss this functionality.

+1 to higher the priority

Hi Folks,

as Sirko said correctly, we`re in our QA Department aren`t easy able to distinguish if all assigned branches get the whole commit set. The Old approach was quite perfect maybe its possible to transfer the old information into the new look and feel?

Br,
Steffen

Hi,

same here, but our QA team needs this information. Is it possible to get the commits tab enabled?

Thanks,
Sirko

Hi,

same here. It takes a lot more time to get the information about the branch where the commit has been pushed to and it is really important information for us.
A workaround until this has been put into the development panel would be, to allow the commit tab back. I would rank / priority a lot higher, as a supposed improvement proves to take informaiton away from users.
Regards
Holger