Why are JIRA issues from branches not showing as linked to Bamboo builds and releases?

First, we are creating a new branch from JIRA in bitbucket and leaving the JIRA key in tact. As an example, a new branch might be UNITCLASS-5-code-cleanup.

Then, we are fixing the issue, creating a pull request, and merging into the main branch.

Then, Bamboo builds it. However, it does not pick up the affected JIRA issues under the build or release.

So we have this commit message which is detected as a new change for the build:

Merged in UNITCLASS-5-code-cleanup (pull request #9)

However, there are no new JIRA issues reported. It does see a JIRA issue linked if we explicitly add UNITCLASS-5 for example to the commit, but not if the commit has the full branch name, including the JIRA key.


Why is this not showing up?

1 answer

Isn't that the right behaviour? The regular matching done for JIRA issue key definitely looks for a whitespace after the issue key. So the commits that you do in the UNITCLASS-5-code-cleanup branch should include the issue key (UNITCLASS-5) so that this match is successful.

For our workflow, it seems to make sense that when UNITCLASS-5-code-cleanup is merged into master, that it is finished, so we want it to appear as fixed.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

914 views 3 9
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you