CSV Import but no option of issue key or issue ID to map issues to

[Rashad Carter]

Hi all - I'm attempting to do a CSV import into an existing project. I'd like to import both tasks and sub-tasks into that project. I don't see an option in the drop down for Issue Key or Issue ID in order to associate the sub-tasks to the parent tasks. Is there a reason why?

[Ron Lupone]

I am having a similar problem. and those 2 articles... I dont think cover my scenario. I want to update existing records in JIRA. I exported the file  to CSV. made and update 1 one field and now want to import the file to update the records.  I am not adding subtask or the like. My csv has Issue Key, but when I try to select Issue Key, there is no option in the drop down. Just Issue Type.  What am I doing wrong?

[Bert Dombrecht]

There are two versions of the CSV import in Jira:

1. Regular CSV import: via "Search work items / ... / Import issues from CSV"

2. Admin CSV import: via "Settings / System / External System Import"

Only the Admin version (requires product admin permission) allows an update by mapping the issue key.

Could it be, you are using the "Regular" import?

Alternatively, if you want to update a field to the same value for a number of work items, you can use the "Search Work items / ... / Bulk change issues" (requires "Make bulk changes" global permission).

[Bert Dombrecht]

I have encountered the same problem. For a specific project my user was not able to map the Issue ID field to link Sub-tasks to their parent in one upload file.

I found out that you need to put the 'Linked Issues' field on the Create screen of your project. Then the Issue Id field can be mapped during a regular CSV import.

I hope this helps.

[Sandhi Trivedi]

Can you please elaborate on this ?  "you need to put the 'Linked Issues' field on the Create screen of your project." 

What do you add in the Linked Issues field ?

[Bert Dombrecht]

Hi @Sandhi Trivedi ,

When you import work items from CSV via the regular CSV import (Search work items / ... / Import issues from CSV), the field mapping relies on the fields being available on the Create screen of the target project.

For example, if you want to map a CVS column to the Components field, the Components field needs to be on the project's create screen.

If you need to link sub-tasks and parents in one upload file, you need to map the Issue ID and Parent fields.

The Issue Link mapping in the CSV upload wizard only becomes selectable if the "Linked Work items" field is on the target project's Create issue screen.

The create issue screen:

Import from CSV:

Mapping the Issue Id:
This is not available if the "Linked Work items" field is not on the target project "Create" screen.

[Aaron Pavez _ServiceRocket_]

Hi @Rashad Carter 

Here are two good posts about what you want to do:

https://community.atlassian.com/t5/Jira-Service-Management/Subtask-creation-via-CSV/qaq-p/1922797

https://community.atlassian.com/t5/Jira-Service-Management/Import-sub-task-from-CSV-file/td-p/1751443

Regards