How to import sub-tasks

[Chuck Kandzierski]

I create tasks every month using a CSV "template".  The template creates Tasks and Sub-tasks.  The sub-task creation hasn't worked correctly since Atlassian redefined the Parent field.  I used to create the task and then use that Issue ID as the parent value for the Sub-task.  I've seen Parent Issue ID as a potential column header to replace Parent but I don't see a corresponding field when I do the configuration.

I am using the legacy import method.

[Mohanraj Thangamuthu · Accepted solution]

Hello, Good day. While importing make sure to map the issuetype to "Sub-task" and parent field is mapped. Thanks

[Nikola Perisic · Accepted solution]

Welcome @Chuck Kandzierski 

You might find this article helpful: https://community.atlassian.com/t5/Jira-Service-Management/Anyone-else-having-issues-importing-sub-tasks/qaq-p/2554386

[Chuck Kandzierski · Accepted solution]

To summarize

 - Whereas we used to be able to create tasks and their sub-tasks in one import we now must use two imports.

 - Import 1 - Import the tasks.  The parent should be the epic if you are using epics.  The issue key and issue ID will be automatically assigned.  Save the log as you will need it in the next step.

 - Import 2 - Import the subtasks.  Get the appropriate parent ID for each subtask from the Task log.  Fill in the issue key and issue ID picking up where the Task log leaves off.  In other words if the last Task created has ID 1000, the first subtask should be 1001.