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

Question

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?

John Funk · Answer

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.

Michael Main · Answer

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.

Bill Sheboy · Answer

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