Connection two issues to one branch

[S.K.]

Hi, is it possible to link two issues to one branch? 

[Andy Heinzer · Accepted solution]

Hi,

I understand you have Jira Software server connected with another developer tool like Bitbucket, and are looking to see if you can have a single branch that is then appearing in the developer tool panel of two Jira issues.

Yes this is possible.  However in order to make this work, the branch name has to contain both Jira issue keys (ABC-123 or XYZ-555 as examples).  This is also explained in Integrating with development tools in the "How it works" section.  From that section:

• Commits are linked automatically if the issue key is included in the commit message.

• Branches are linked automatically if the issue key is included in the branch name.

• Pull requests are linked automatically if the issue key is included in the pull request's title or in the source branch name.

• Reviews are linked automatically if the issue key is included in the title of the review, or if the issue is linked from the review.

• Builds and deployments are linked automatically if a commit involved in the build has the issue key in its commit message. 

I tested this out recently myself.  It does still work. The thing I found is that these issue keys have to be in the branch name, and the only time it looks like you can set that value is when the branch is first created.  So I can't seem to find a way to rename an existing branch in Bitbucket, but I have the feeling that is likely by design.

I hope this helps.

Andy

[leodali83]

Hello Andy,

so if I understand correctly, let me say I have two issues: AAA-111 and AAA-112.
In order to view the same branch I'm going to create from Jira, I have to name this branch something like: feature/AAA-111_AAA-112.

Correct?

It's a bit unpractical if I want to link multiples issues or if I would like to name a branch completely unrelated to task's IDs.

Thanks in advance.