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 ;)
How is this an "Accepted Answer" and flagged as SOLVED as it only explains how it currently works and not how to take an EXISTING bitbucket branch and link it to an EXISTING Jira issue.
The answer is YOU CANNOT and you are screwed if you want to do this until Atlassian actually implements this functionality.
This is a Q&A area so where is the feature request section of Atlassian to formalize this as a feature request that can be voted on? As this is a community area that isn't probably monitored well by Atlassian for features.
Someone created an issue, say ABC-123, then a branch was created on a repo to solve the issue, also named ABC-123, yet on the Jira ticket, I only see Create Branch button, and I'm not seeing how to attach it to an existing branch on a certain repo.
Jira shows the repos and branches in the drop-downs, but it only lets me create a new branch even if an existing branch is exactly the same as the ticket ID.
Can someone explain this? Or how to attach the ticket to the branch?
As stated previously in this question, it is not possible. You are screwed if you create the branch first.
That is the point and problem with this question and Atlassian is ignoring the issues brought up here in the question. The request is for a feature to allow connecting a branch regardless of its name and when it was created to a Jira issue.
The safest and best way to link a bitbucket branch to a Jira issue is to use the link in the issue to create the branch which requires the issue to already exist and for a developer to think that you should create branches from issues and not from Git CLI or Git tool of choice. Alternative mentioned seems to name the branch the same as the issue exactly in a specific manner, however that may violate many branching naming conventions companies and teams already have in place. However, using that link on the issue will name it this way also thereby violating the same conventions most likely as well.
For example, if you click the create branch link you get the following:
It has a max length of 40 characters total so will be truncated and IMHO looks like crap.
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.
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.......
Hi everyone! My name’s Matt and I’m a product manager at Atlassian. I work in the navigation & findability space for all our Jira Cloud products. We’ve been working on trying to improve the exp...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events