Create issues with CSV import - issue key

[Crystal Baker]

Is there a way to map issue key when creating issues? I need to move my issues from one instance to another and I want to preserve the issue key (not just the issue ID). For example, AUTO-23 needs to remain number 23, and not reset back to AUTO-1.

I'm also curious about importing comments, as I don't see those configurations present in the csv import. 

[Nic Brough -Adaptavist- · Accepted solution]

I'm afraid you can't do this with the CSV import.

It doesn't care what issue key you want, it imports issues in order, one line at a time (top to bottom through your csv), and uses the same logic that "click create, get issue" does when numbering - it takes the next one.

Mapping the issue key only has an effect when you map an existing issue key.  If Jira finds an issue with that key in it already exists, it assumes your import is an edit for that issue, not a create.

There is a way you can trick it, but it's a fiddle.

Let's say your AUTO project has got issues numbered up to, and including AUTO-20.  If you give it CSV that maps the issue key to AUTO-23, then it will create it as AUTO-21.

If, however, you feed it CSV liske

• Project, Summary
• AUTO, placeholder-21
• AUTO, placeholder-22
• AUTO, Actual summary for Auto-23

You'll get the right numbers out of it.  After import, delete AUTO-21 and AUTO-22

[Alessandro Lombardo · Accepted solution]

Are you jira-administrator? @Crystal Baker 

[Crystal Baker]

Yep. I keep wondering if my file is set up incorrectly. The fields definitely exist in my destination project.

[Alessandro Lombardo]

Did you try to tap "key" and in the bottom of the list appear issue key?

[Alessandro Lombardo]

was my reply helpful? @Crystal Baker If yes, please accept my answer please ! thank you very much :)

[Crystal Baker]

Unfortunately I still am not getting that field. I think it's because its a brand new project and there are no issue keys yet.

[Meg C]

Hi @Crystal Baker did you ever get a solution for this?

[Nic Brough -Adaptavist-]

@Meg C Welcome to the Atlassian Community!

There is no "solution" beyond what I posted before.  You have to create your import file in a specific order and fill in any blanks, and accept that importing into a project means that you have to have issue keys that match the project-sequence that Jira works with.

[Crystal Baker · Accepted solution]

Thanks all! I got it. You do need to do the import through the Administration > System menu, not at the project level. If you're creating through project import, it will not allow issue key to be mapped. However, if you're a jira admin, you can override the mapping and select issuekey as many have indicated via screenshots above. 

Tricky and not obvious, but it ended up working out. Thank you all so much for these comments!

[Craig Nodwell · Accepted solution]

Hi @Crystal Baker welcome to the community.  Use Issue Key.  Here's a document to help with understand csv imports.  

[Crystal Baker]

Hi! I appreciate your help. Unfortunately issue key is not a field in my list of choices. 

[Crystal Baker]

Update: it's because I wasn't logged in through the systems permission - I was only in automation from the project menu. You have to be logged in as an administrator and access the import option from the System menu, in order to use system fields.