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.
Hi Team, I'm exactly facing the same issue which is raised by Dave in the above, my all other stories are properly showing "1 branch" into the JIRA but there is one story ABC-123, which does not show up into the JIRA, it just say "Create Branch". Even though I've created the branch post the sprint planning meeting for all stories. Please help us, In JIRA there should be definitely a provision to link the story with the same story branch.
It is possible to see the Bitbucket Cloud branches associated with the Feature/Story in Jira Cloud.
You have to make sure you establish the connections between Jira and bitbucket properly (each product needs to be aware of the other). There is a sync involved.
On the Jira side you go to Admin | Jira Settings | Products | DVCS Accounts
This sets up the sync.
This is really a missing feature, Microsoft's Azure DevOps does have this.
But you could use Smart Commits to link issues?
This might help (replace XXX-123 by your story id):
git commit --allow-empty -m "XXX-123 Linking commit to story"
Will at least result in a linked commit... it's not much but at least you could find the work done if required
This is a lot better, just rename the branch (https://multiplestates.wordpress.com/2015/02/05/rename-a-local-and-remote-branch-in-git/) and it will be linked to the issue.
Note that you can link multiple issues by adding multiple issue id's in the branch name. For example:
So an issue I've got is that in my organisation, we are restricted to naming our branches:
(where XXX-nnn is the Jira tag)
So that they may be deployed on our Jenkins pipeline. This does not allow the format: XXX-nnn-whatever.
Does that mean that I'm Screwed (to quote above!)
@Bill Naylor , just having the Jira ticket ID in the branch name should work fine. It doesn't have to be at the front of the branch name. At one point, I was even able to put two ticket IDs in the same branch and both Jira tickets eventually recognized the branch as belonging to both.
Note that this happens eventually. Don't expect it to show up immediately in Jira after you've pushed your changes.
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.
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.
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:
Log in and click More|Vote to add your desire to the ticket: https://jira.atlassian.com/browse/JSWCLOUD-18105
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.......
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.
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