Multiple JIRA issues keys in one commit message


While committing a code changes with a JIRA issue number I can see the code changes in that specific issue. However, I want to add couple of JIRA issues in a commit message but see the changes in just one of the bugs. As now, I am seeing the same changes in both of the issues. 


Is there a way to make the commit changes being seen justs for the first issue key and not for the rest of the issues mentioned at the commit message?


4 answers

1 accepted

0 votes
Accepted answer

It seems like it's not possible, unfortunately, according to this documentation:

I think that you would have to create separate commits for the bug you want to have the message attached in the commit and for the other ones.


cheeky Boooo...Fogbugz can do it.

Hi Darly,

As per your description I think you actually want to have a commit associated with only one of these issues, and not have any commit associated with the other issues, is this correct?

In fact as pointed by Andre it's not possible to ignore the other issue keys you put in the commit message, but I'd like to ask you the purpose of not having the commit associated with the other issues. At first I see a commit associated with one issue, and it may be associated with more than one, as in your case, but if you don't want to link the commit to every issue, I thought about linking the issues among themselves directly in JIRA, as per the Linking Issues document, and then performing the commit against only one of these issues.

Please let us know if you believe the above matches what you are intended to do.


Gustavo Refosco

Gustavo, The reason is the Code Reviews. Sometimes some developers had a set of JIRA issues (more than one), that just require one changeset (or code commit). And by mentioning these issue key numbers in one commit message: (1) That commit will appear in every issue mentioned in the message and (2) Since the Crucible code review is based by a JIRA issue number AND by SCM's revision id, the code review will appear in all these issues and consequently, it might create confusion and conflict between code reviewers because for a JIRA issue, some activities is not complete. And closing/completing the code review for one issue can interrupt the code review for other JIRA issues

That's why I am more partisan of a code review linked to a JIRA issue instead of the commit revision number

0 votes
Andy Nguyen Atlassian Team Apr 17, 2015

Hi Darly,

I'm aware of some users using -DEMO-1 (prepending a Hyphen), to avoid linking a commit to the JIRA issue DEMO-1. So the commit message may be like "not linking to -DEMO-1".

DEMO-1 won't appear as a link in Fisheye as well as in DEMO-1's Development Panel in JIRA. However, the commit is still silently linked and appears in the deprecated Source tab, if the tab happens to show up in the JIRA issue (not an usual case).

By that I mean, you can still use this workaround to some extent.


As I seen at the answers and discussed with the team, we will use a workaround that we can mention to just one JIRA issue correctly and the others user as DEMO#1 in our SCM commit message. 


Thanks all.

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 ...

952 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