Using csv import to create new tasks with existing epic parent

[Scott Totman]

Hi there, I've seen a lot of threads about creating parent-child links using the csv import but I haven't got the specific answer I need.

I have JIRA admin permissions. I am working with Company-managed software projects.

I have created Epics in JIRA. I am now trying to use the External System Import (the old one, not the 'new experience') to import a csv of Tasks that need to be created on import under existing Epics.

I know I need to use a combination of Parent, Issue Type, Issue Id (or Parent Id, or Parent link) but all my tests successfully create tasks on import but do not create the parent link with the existing Epics.

Ideally what I want to know is:

1. The correct columns I need to include in the csv and what information needs to go in each column.

2. The correct mapping of csv columns to JIRA fields during the import set-up.

If anyone can share a screengrab of a correctly set up csv and the correct import JIRA field mapping that would be amazing.

[Marc - Devoteam]

Hi @Scott Totman 

There is a KB article on CSV import.

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ 

If you want to link new issues to existing epic's

There are 3 columns are mandatory, “Issue id”, “Issue type”, and “Parent”

If your Epics are already in the system, these need to be updated. make sure to have the keys of the epics specified in a key column in your csv as well.