What is the correct format for the Jira Parent field when importing from Excel?

[Colum McAndrew]

I'm trying to create multiple Jira tickets using a CSV file. I'm getting errors when trying to do so saying the Parent field values are invalid, but I'm using the format suggested in the import wizard. The parent is in a different project from the one I'm importing to. Would that make a difference?

Also I was trying to set the ticket status to "To Do" but I can't seem to find a Jira field to map this value to. Is this possible, or does the import wizard only allow a Backlog status?

[John Funk]

Hi Colum - is this a Team-managed or Company-managed space/project? Can you share a screenshot of the csv you are importing (just a couple of lines).

[Karan Sachdev]

Hey @Colum McAndrew

Good day!

Are you using the old import experience to map Epic and child items during the import? If so, you might be impacted by this bug: https://jira.atlassian.com/browse/JRACLOUD-96848

The workaround is to use the new import experience, which will create a new space and import the work items. Once done, you may bulk move those work items to the desired work space. Reference: https://support.atlassian.com/jira-software-cloud/docs/move-multiple-issues/

[Marc -Devoteam-]

Hi @Colum McAndrew 

@Ajay _view26_ is right here, but also I will remind you that you need to have access on that project, as your import wants to execute "edit" actions on existing issues.

[Ajay _view26_]

Hi @Colum McAndrew 

Yes, that can make a difference. For CSV import, Parent usually needs a valid issue key that the importer can resolve (e.g., ABC-123), and cross-project parenting is only valid where Jira supports it for that issue type hierarchy