How do I import the Sprint and Parent values using the old Jira import tool

[Chuck Kandzierski]

We use sprints and Epics (now known as Parent) in Jira and we import a list of repeated tasks every month.   With the implementation of the new import tool and the reuse/rename of Epic to Parent the import doesn't work as it used to.

What are the column headers and the values that should be placed in the columns for Sprint and Parent (remember that in our world this is actually an Epic).

[Bill Sheboy]

Hi @Chuck Kandzierski 

Just to confirm what changed for the sunset of the "Epic Link", "Epic Name" fields...

• Epics are still called Epics
• the "Epic Link" field was deprecated, and the "parent" field is now used for all parent / child relationships
• in an import, use the "parent" field when mapping the import for the child work items to connect to a parent

To learn more, please see this knowledgebase article:

https://confluence.atlassian.com/jirakb/keep-issue-parent-child-mapping-during-csv-import-to-jira-cloud-1096095688.html

Kind regards,
Bill