Issue ID vs Issue Key

I'm creating a CSV file for importing into JIRA and I noticed I can choose between Issue Key and Issue ID to map values. What is the difference? Are Issue Keys used for standard issues and Issue IDs used for sub-tasks?

3 answers

1 accepted

1 vote
Accepted answer

The issue key can change, the ID is immutable. E.g. I create issue ABC-123 with an ID of 10105, and move it to project XYZ, it'll become XYZ-789, but the ID remains 10105

is this still valid with ondemand & clustering?

Yes.

issue keys and ids are automatically generated by Jira during import.

Do not map those values in CSV for new issues unless you want to update some custom fields for existing project issues

Er, not quite. If you use one of them, it will cause your import to try to treat the CSV as an update on an existing issue, rather than create a new one.

I modified my comment. :)

On that note of treating a CSV as an update and on an existing issue rather than creating a new one. I have the issue key correlating to existing tickets and when I upload, I check "map exact field" but it is still creating new tickets. 

Any insights on how I am mapping this incorrectly?

Hi Lindsey ... 

Just wondering was this resolved, if so, how?

Thanks

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

1,095 views 4 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