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
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.
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.
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 ;)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs