+1

still a desirable feature after 5 years  

+1

+1 

Just been forced to move from azure devops to BB - like going back in time... It's just a link to the branch in git, you can have one ticket and many branches that resolve that ticket (UI, API, infrastructure) Maybe the devs that work on BB don't actually have to use it? Oh and don't get me started on the lack of dark mode...

+1

+1

+1

We also need it

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

ery helpful. It's easy to forget to look at the Jira issue key when creating the branch, and I don't want to have to remember to create the branch from Jira instead of just creating locally, then pushing the branch which is much more natural.

+1

+1

+1

+1

+1

I would love if we could use the 'Labels' feature to be able to reference the Jira ticket and then have Jira just pick that up. Then multiple branches which have resolutions to multiple tickets could be used.

+1

+1

+1

+1

+1

+1

+1

+1

+1

It should work with GitHub integration as well

Could be a real game changer

This feature is absolutely needed. In my workflow branch is created with a milestone name and almost always does not map to a single issue. We fudge it by creating Epic issues to match the branch name but this in itself creates additional challenges. There must be a clean way in Jira to just link ANY commit without need to use the Jira issue key in the commit name. Please put some priority into this and thank you. Peace.

I'm an intern and this is part of my project requirements help Jira devs I don't wana get fired

+1

Please add it!
Either that or make renaming of branches via the Bitbucket UI easier in order for us to retrospectively include the issue key in the name ☝️

+1 for this

please add this feature it is much needed!! 

We don't want this, but we need this That is how necessary it is.  
+10000

Trello can do this easily, just ask them!

Would love to have this feature!! It really hurts our team not having the correct way to integrate our branches

This is one of the first issues I ran into when transitioning to Jira. The lack of this feature struck me as quite non-intuitive. We have numerous smaller feature branches, sometimes at finer granularity than our Jira tickets, and our branches often align with less formal issue tracking tools (e.g. Asana) that tell "the real story", and then we link them up to Jira issues which tell "the pretty story". I find Jira's present association policy rather presumptuous.

Just had a need for this last week as a branch relating to one ticket also fixed issues relating to another ticket, so it would have been nice to be able to link that branch to both of them. I however could link the pull request to both of them, so that was helpful!

This would certainly be nice to have for us as well!

This would be a huge benefit. Shared branches are the rule for my team, and we work on multiple features at once.

This functionality would be helpful to my team.