Why is IssueKey not available to map to during CSV import of linked field values for existing Issues

[Wayne Rice]

I am trying to following this guidance from your site (link below) for importing via CSV file for linked issues relationships.  I do not find the IssueKey value as an option to map to during Step #2 below of the CSV import process, as shown in the help example. 

Excerpt below from site page -  https://confluence.atlassian.com/jirakb/import-issue-links-from-a-csv-file-in-jira-server-740262715.html

However, you need to ensure that users are not actively creating issues on those projects. We usually see that it's easier to follow a two-step approach in such scenarios:

1. First, create the issues using one CSV file;
2. Import the issue links using a separate CSV file, using the issue keys you obtained after the step above.

[Pramodh M]

Hi @Wayne Rice 

You don't need to map the Issue Key if you are not editing any existing issue

You would map the links type to the issue key if you want to link the issue which you are importing the existing ones

Here's the format

Summary,Issue Key,Blocks  ,Clones

Issue1,TEST-1    ,TEST-2  ,    

Issue2,TEST-2    ,        ,TEST-3

Issue3,TEST-3    ,        ,    

https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-in-jira-740262715.html

Let me know if this helps

Thanks

[Wayne Rice]

Hello - still a little confused. I am trying to link an existing issue to an existing issue. It sounds like your guidance assumes that the original issue that is being linked from does not yet exist, but in my case it does. I am confused as to why Summary needs to be mapped if the original issue already exists, as do the issues that are being linked to.