Importing sub-task via csv

[Mario Nikolov]

Hello, I have been trying to import some sub-tasks but unfortunately without success. I have read most of the articles regarding this but still could not understand it quite.

An example with a csv and mapped columns in the import will be much helpful and appreciated.

BR
Mario

[Valerie Knapp]

Hi @Mario Nikolov , thanks for your post.

Please refer to this other post - https://community.atlassian.com/forums/Jira-questions/How-to-import-sub-tasks/qaq-p/2919995 

Basically, you need to map the sub-tasks onto the Parent tasks in the import file so you will likely need to do an export of the parent work items.

Steps:

1) Define a list of parent work items

2) Export the parent work items in csv

3) Define the columns you want to populate in the sub-tasks and create a csv file

4) Define a column in the sub-task csv import file for the Parent. Here, you should indicate the mapping of the Parent issue ID / key from the export in step 1.

5) Try to import your sub-task csv file, using the wizard

When you say you are not having success, what is going wrong? You import the file and map the columns and the sub-tasks aren't created? Are they created instead as tasks / independent work items? Where are you getting stuck?

If you are getting an error message or screens, please can you share those?

Best wishes

[Mario Nikolov]

Hello, Valerie

Thank you for your response!

When trying to import the tasks i can only see two options related to the parent("Parent" and "Parent Link"). BY selecting Parent this is the error I receive.

BR
Mario

[Valerie Knapp]

Hi @Mario Nikolov , thanks for your feedback.

I just went and tested this myself and I agree, it is not very clear.

I make you a short Loom which shows you how I got it to work.

https://www.loom.com/share/4a1f039a85884661bbbaf52705c420e5 

My original file is like this.

As I suggested to you, I just exported all of the work items from a space.

Then, I filled in the columns, 'Issue type', 'Summary' and 'Parent key'.

Issue Type

Issue key

Issue id

Summary

Assignee

Assignee Id

Reporter

Reporter Id

Priority

Status

Parent

Parent key

Parent summary

Sub-task

Test1

64068

SALES-15

Sub-task

Test2

64069

SALES-16

Sub-task

Test3

64067

SALES-14

Sub-task

Test4

64068

SALES-15

Then, during the import, I had to map the issue type to work type, the summary to summary, the Parent key column to 'parent' and I had to map the Issue id column from my original file to the Issue ID in the system, even though it was empty / as we are trying to create new work items.

Please have a look at the Loom and try it yourself.

Hopefully this helps you.

Cheers