Anyone else having issues importing sub-tasks?

[Rosa Santos]

This was working for me about a month ago. Nothing has changed with my CSV file or my headers - and now getting this error:

• Issue can't be created due to the error/s [ Issue type is a sub-task but parent issue key or id not specified. ]

[Joey Bautista · Accepted solution]

Hi,

I was having the exact same problem as you. I noticed that the field mapping page listed parent as "Do not map this field" even though it was defined in my configuration file. I manually mapped it to the right field on my CSV and then uploaded it successfully. 

When I compared the two configuration files (my original) and the one for the above upload, it looks like the backend jira field name was re-named. It was "subtask-parent-id" and now it's just "parent".

I saved this config file and tried to upload again and it worked like normal.

[Asha Goyal · Accepted solution]

Hello @Rosa Santos 

From the error given, it seems that you are trying to import the subtask via CSV, and for that it is mandatory to provide a parent issue key. Every subtask must have a parent issue, and without them, subtask cannot be created in Jira. 

Make sure that either parent is already exist into the system, and if not please break the CSV into two parts. In the first go Import the parent first, take the parent Issue key from Jira and then import the subtask subsequently.

Tip -- Make use of label while importing to identify the recent issues imported.

I hope it helps.

Please accept my answer if it found useful.

Thanks

[Joey Bautista]

This is really inefficient. 

I used to be able to import stories and subtasks together using a dummy Issue ID (e.g., PROJ-99999). I would just have the Issue ID filled in for the Story and left blank for subtasks but Parent ID blank for story and filled in (e.g., PROJ-99999) for subtasks.

It all loaded at once but now I have to do a two-step process to import? That's terrible.

See my answer separately. This isn't the case.

[Erich Heerdt]

@Joey Bautista 

So did you get your import file to work with items and subitems in the same upload? I had to first build a file with items, then export that file and Vlookup the parent names to the subitems to fill in the item#, then import the subtasks.

When I try to import both, the validation errors out on all subtasks saying no valid Parent ID could be found. I tried making a dummy item # for every item and subitem and using it filled in correctly for the parent field, but that didn't work.

(I'm importing lines from Monday.com to Jira Work Management)