CSV Uploader (Import Wizard) - Mapping Parent / Epic properly

[Quentin MD]

And here we go again for another EXHAUSTING Jira issue that would literally be solved in 5 minutes with any other software... Enough ranting, let's get down to business...

I've been using the CSV Import Wizard a few times already, with more or less success.

It looks like I finally got a structure that gets me 90% of the work done...except for MAPPING AN EXISTING PARENT (EPIC) TO A TASK.

I've just exhausted all my options and would love a CLEAR answer at this stage:

1. Which field should I use to map an existing PARENT / EPIC to a new task: Parent ID? Epic Name? Epic Link? Else?

2. How should I enter said Parent/Epic in my CSV? Literally: how should I write it down? The name of the Parent Epic as it is displayed in the backlog (say, "Cloud Infrastructure")? The way it is displayed in the "Issues" table of the project (eg, "JIRA-1234 Cloud Infrastructure")?

Thanks for your support everyone!

[Gerusa Lobo (e-Core) · Accepted solution]

Hi @Quentin MD 

In any csv issue import you must be mapping the issue.summary.

Also, It they are existent issues or you want define the key, the issue key too.

My recommendation to import csv with Epics, you need import the Epics first, and after the storys or tasks.

You can use this kind of format:

Best Regards.

[Quentin MD]

Hi Gerusa,

Thanks so much for your reply and for the screenshot.

FYI, I'm using JIRA Cloud.

This is what my CSV upload file looks like:

As you can see:

• I filled up the Parent "ID" in the Parent column, which I've then been mapping to the "Parent" field in the CSV Import Wizard. I tried with the "ID" only (what you're seeing above in my screenshot) as well as the full Parent name (eg. "JIRA 7305 Merchant Boat"): does not work in any case. This is the error message I'm getting at the end of the import process: Unable to retrieve issue key for parent : JIRA-7305.
• You can also see the empty Issue Id column that I needed to add, otherwise I got this weird message during the import process and cannot proceed to the import: You have to define which CSV column maps to Issue Id if you want to import parents.

Now, are you telling me that I need to CREATE THESE ISSUE IDs MANUALLY? But what if I'm using one that's already been created? Won;t there be a conflict?

[Gerusa Lobo (e-Core)]

Hi @Quentin MD 

I 've tested in jira cloud import csv.

Try import the ParentKey as Epic Link in Wizard.

The Epic mapped was already created in Jira Project.

Let me show my test file:

Wizard mapping:

Issue created:

Best Regards.

[Quentin MD]

YOU DID IT GERUSA!!!

The Parent / Parent ID / whatchamacallit needs to be mapped to EPIC LINK in the CSV Import Wizard.

Why have all these fields available if they're not even working.

Why saying everywhere that Epics have been replaced by Parents when the CSV Import Wizard is still very much using in legacy mode...?? Thanks Atlassian...

You saved my day Gerusa!

Enjoy your weekend.

[Vishal Biyani]

@Quentin MD 

In Cloud, parent field should be used.

In the CSV import file, you can provide existing Epic Key say JIRA-1234

if this does not work for you, please share the CSV input file format (i.e. column names) and the screen shot of the screen where CSV Columns are mapped to JIRA Columns.

[Quentin MD]

Hi ,

FYI, I'm using JIRA Cloud.

This is what my CSV upload file looks like:

As you can see:

• I filled up the Parent "ID" in the Parent column, which I've then been mapping to the "Parent" field in the CSV Import Wizard. I tried with the "ID" only (what you're seeing above in my screenshot) as well as the full Parent name (eg. "JIRA 7305 Merchant Boat"): does not work in any case. This is the error message I'm getting at the end of the import process: Unable to retrieve issue key for parent : JIRA-7305.
• You can also see the empty Issue Id column that I needed to add, otherwise I got this weird message during the import process and cannot proceed to the import: You have to define which CSV column maps to Issue Id if you want to import parents.

Now, are you telling me that I need to CREATE THESE ISSUE IDs MANUALLY? But what if I'm using one that's already been created? Won;t there be a conflict?

[Yousif Hassan]

Use Parent ID and then put the Issue Key of the parent in - the make sure you the attribute Parent ID = Parent ID when you are mapping the data. 

Also if you can share the field mapping + errors you see, that would help debug further if the above doesn't work.