almost 7 years later and now update. Why can't it be possible to allow Issue-Key mapping using CSV import and activate issue updates (instead of creating new issues)?

4 years later and this behavior still standing... 

Confirmed - if you add Issue Type field on the Create screen (even though it's unusable for normal issue creation), you can use Issue Type in CSV import.

I created new tab for this field with the name "." for this so the issuetype field is basically invisible from view for normal users when they create issue in usual way (or at least for those who don't have OCD so they don't immediately see every unusual pixel on screen ).

(thanks, Jason Kemp)

UP!

This is a must-have feature!

I have identified a side effect: If you don't set issuetype, the mapping "Parent key" is useless, therefore you cannot import issues as sub-tasks as well.

@szabolcs.keri@ni.com - how did Gergo Papp solve this issue?  I still have the same problem (mapping issue key)

Hi Szabolcs, can you please let us know how this issue was solved? I'm still facing the same problem.
Thanks

Hey,

meanwhile Gergő Papp has solved this issue. Please ignore my request. Thnx.

Hey Guys,

Can somebody help me to have this IssueType link to work for end-users(like me)?

Right now cannot find the corespondent JIRA field for it.

We have many projects to deal with in Manufacturing area and would be desired to use this feature on our own - without to ask for IT help to make it ...or do additional extra steps (do Bulk move after import).

Could you give an estimation on whether is an option fix this gap, please? Thanks, Szabolcs.

@Jason_Kemp, This issue is about not being able to set the IssueKey.  I was hoping that you just mistyped, as I am running into this same issue, and I attempted to add the 'Issue Key' to a screen, but was unable to.

I really hope that this issue gets implemented, it seems like my only option in the interim is to implement my own 'create or update import' via the rest API.