Unable to map Parent ID when using the CSV import to create subtasks

[Michael Main]

Hello, I'm trying to import issues using a CSV file to create multiple subtasks, but it can no longer map the Parent ID field.  I've used this format many times in the past, but now it's not recognizing this field.  Has something changed with this tool or that field?

[Bill Sheboy]

Hi @Michael Main -- Welcome to the Atlassian Community!

Please see these related defects for that symptom, which appears to have started / worsened since the addition of the "new" external import and the sunset of several Epic fields to unify the parent / child relationships:

• https://jira.atlassian.com/browse/JRACLOUD-81997
• https://jira.atlassian.com/browse/JRACLOUD-84679
• https://jira.atlassian.com/browse/JRACLOUD-92272

Kind regards,
Bill

[John Funk]

Hi Michael - Welcome to the Atlassian Community!

Are you running the importer through the path of 

Settings > System > External System Import

If not, or if  you are running it through the project or search function, try running it through the above path (use the old version if it asks). 

[Michael Main]

I'm accessing the importer through an issue filter search.  I'm not an admin, so I don't have access to the above path.  We use this rather frequently, so wanted to continue to self serve if possible.  

[John Funk]

Yeah, Atlassian has changed a bunch of things with that process in the last few months. If you get the CSV to an admin see if they can run it for you. Many things will still work the way you are going but not everything.

[Richard]

You may be able to find some helpful answers in the following articles:

1. Unable to find the IssueID and ParentID fields when importing parent-subtask relationships via External System Import - CSV | Jira | Atlassian Documentation

2. Solved: Subtask creation via CSV

Mainly this is because subtask-task parent relationship is not exactly the same as parent-child relationships between other issues types.