nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Linking an existing branch in Bitbucket to a Jira issue?

Peter Civitarese

Hi,

Have been using JIRA/Confluence Cloud and Mercurial on separate server

We have just moved to Bitbucket Cloud and linked to JIRA that is working ok.

Within an a JIRA issue, there is an option to create a "Branch" in Bitbucket. This appears to work fine for new branches moving forward and that it displays the link to the branch from within the JIRA issue.

How can you link an existing JIRA issue to an existing branch in Bitbucket so that within the JIRA issue it displays the link. Within the issue it only has the option to create a new branch, not link to an existing Branch.

Have search forums and have not come across an answer for this.

If this has been answered somewhere, can you show me the answer?

Thanks in advance

Accepted answers

Jobin Kuruvilla [Adaptavist]

JIRA uses a simple technique to link issues and branches - You need to have the issue key in the branch name.

When you create a new branch, JIRA automatically adds the issue key in the branch name. Even if you create branches outside of JIRA with the issue key in it, they will appear in JIRA. But that also means that you cannot add existing branches unless you rename them to include the issue key.

All comments

Jobin Kuruvilla [Adaptavist]

JIRA uses a simple technique to link issues and branches - You need to have the issue key in the branch name.

Peter Civitarese

Hi Jobin,

Thanks for reply.

"When you create a new branch, JIRA automatically adds the issue key in the branch name. Even if you create branches outside of JIRA with the issue key in it, they will appear in JIRA."

We are aware of this. Our point was more linking existing Jira Issues to an existing branch that was already created.

"But that also means that you cannot add existing branches unless you rename them to include the issue key...."

We tried to preform this action to rename a branch to include the Issue Key, but was unable to to do this. Is this possible? if so how?

Our last option was to close the existing branch and recreate, or create another branch and merge. messy and one we were trying to avoid.

Peter

Jobin Kuruvilla [Adaptavist]

There is no easy renaming of branching in git. I think the proffered way is to rename the local branch, delete the remote branch and then push the renamed branch.

In Bitbucket, you can probably create a new branch, with the new name, from the existing branch and delete the existing branch.

But yeah, no easy solution I am afraid, unless you add a plugin to do it in one click

Peter Civitarese

Ok, Could be improved as I'm sure I would not be the first to raise this type of question.

Thanks once again.....

Martin Kunz_x399w1

Definetely would like to see this improvement/enhancement also. We have a lot of branches, which are not connected to our Jira-issues.

Nathan Pisarski

I would absolutely love this feature. This is one of those features that I thought it was so simple that it wouldn't need to be specifically asked for.

Coming from Visual Studio Team Services (the bottom of the issue tracker food-chain), I thought this functionality was a base necessity.

I don't like the idea of polluting the git history / branch list with a bunch of JIRA-specific stuff. It just feels like abusing Git for the sake of a third party. To make an analogy, it would be like if Skype used an IRC channel with special commands like `<emoji>100</emoji>` to transmit text. IRC communication should be plain-text just like git commits / branch names should be idiomatic for Git, NOT Jira.

Daniel Soares_o2b83p

I would like to see this improvement/enhancement also. We have a lot of branches, which are not connected to our Jira-issues.

Daniel Soares_o2b83p

There is a tip how to link the issue on Jira to the repository on Bitbucket. https://confluence.atlassian.com/bitbucketserver/automatic-branch-merging-776639993.html#Automaticbranchmerging-ordering
I hope you enjoy.

Peter Civitarese

Hi Daniel,

Great to see the reference link for merging.

The link documentation is for JIRA server, we are on JIRA cloud. As we have experienced, there are some solutions for Server that can not be used on cloud and vice versa. If there is an equivalent reference for the cloud version, would be great to see it as suspect many others. I have not come across one yet.

Hint: @anyone at Atlassian listening.......

Cheers

Peter

Daniel Soares_o2b83p

Thank you. I will follow up with cloud customers in order to check if this solutions is applicable and I will search for a reference on Cloud.

Sandeep Guntupalli

Would love to have this feature. Have experienced the frustration a tone of times.

Matthew Janofsky

I created a feature request with Jira to add the ability to associate any BitBucket branch with any Jira ticket(s) regardless of the name of the branch.

This way you could:

Create a branch without having to include the ticket ID as part of the name.
Associate an existing branch with a new ticket.
Associate a branch with multiple tickets.
Associate multiple tickets with a single branch.

Viresh Mathad

You can't view this issue

It may have been deleted or you don't have permission to view it.

Zhenya Kogan

I came here searching for something similar. While not exactly what is being discussed, and I'm working with Github, not BitBucket, but maybe this will help someone.

I needed the ability to add existing pull requests to tickets imported into Jira. I didn't particularly care about branches and commits.

Simply renaming the Pull Request in Github to include the issue id XXX-nnn in the name triggered that PR and Branch to be linked to the Jira ticket.

Anton Ukhanev_lf9trc

If you're using Bitbucket, and only need to link one issue to the branch, here's a work-around:

Create a new branch using the JIRA workflow, i.e. by clicking "Create branch" etc. Name of branch does not matter.
Merge your existing branch into the new branch.
PROFIT!!!111

Anton Ukhanev_lf9trc

Oh, and I've created another issue. Let's try again.

Camilo Jaen

Hello,

To link a branch with a Jira issue make sure a commit message to the branch has the Jira issue id.

This way you can (if necessary) link a single commit to multiple Jira issues.

This works regardless of the branch name or even if the branch name refers to a different Jira issue

i.e.: Proj-1-2001 Disables button after form submission

Hope it was useful

Ishan Mahajan_wxxc64

If you want to link ABC-123 and ABC-321 just create a new branch from whichever you're working on with something like ABC-123-ABC-321-whatever then this branch will be visible linked to each of the above issues.

Daniel Marcolesco

!! HELLO READER !!

This is the correct answer.

Ron Grosberg

We also need this very much! our product uses random seeds to do some of its tasks, which means a bug maybe present on one commit, and disappear on another commit (meaning - the bug is still there there will be on way to reproduce it) - so we need to branch from a specific commit, which means - we can't do it from JIRA UI....

unknown

https://jira.atlassian.com/browse/BCLOUD-17288

Vote for this issue..

Ron Grosberg

I have to say that I felt TFS was much better than bitbucket in a lot of ways

Kevin Dietrich

Correction: This DOES work when tied to CodeCommit. It just takes a few minutes for Confluence to recognize the change.

Tuomo Mäkelä_f86w3i

This works in BitBucket too

bboyairwreck

+1
+ Infinity

Someone from Atlassian at least verify to us that you will put this feature in your backlog. Or give an honest technical reason why you aren't going to.

Stop suggesting to change our branch name or a title in PR. Like the dozen other ppl who explained in this thread for the last two years, this feature request is for linking AFTER the fact PR creation & merge.

Richard Cross

You can add the Jira ticket number in the Pull Request or in a commit; see answers above.

Andy Heinzer

Hi everyone,

This thread has been highly viewed over the years in Community. In an effort to try to help improve the user expectation around this topic, I want to post an updated response here.

As others have already explained in this thread, the way this particular integration feature is designed within Jira and Bitbucket, the branch name has to contain the issue key in order for that Jira issue to display it. This is simple enough to do when creating new branch from Jira's development panel. This is because Jira will automatically add that issue key to that branch name at the time of creation.

However we acknowledge this is not always as easy to manage for existing branches. There are more details about this over in Reference issues in your development work. This is a known limitation of displaying branches. It is only expected to display this branch at the time that branch is created.

Some users find that just creating a new pull request or commit message that contains the issue key can be one helpful way to link those development changes to a Jira issue. But clearly the original question is seeking a solution for an existing branch.

Renaming a branch could help here, however others have noted that this is not always possible, say as in situations where there are outstanding open pull requests on that branch.

For those users that would still want this ability I would recommend watching / voting on the feature request of JSWCLOUD-18105 - Allow linking a BitBucket branch with a Jira ticket without having to include the ticket key in the branch name.

In the meantime, the expectation of this feature always appears to have been in regard to the Jira issue existing first, and then creating a new branch that includes that key in its name at the time of creation. Sorry I do not have a better way to do this today, but if this is important to you, please watch that ticket for updates to this.

Andy

Peter Civitarese

Hi @Andy Heinzer ,

Thanks for the update. after 4 years since the posting, this feature would still be more than beneficial and helpful.

MeijerYoung

What about the ability to add issue aliases for migrations from other bug trackers?

Mechi Fendel_ohpzf6

Add on another 2 years - still waiting for this feature - or has it been incorporated already????

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

bitbucket

atl-gruland