Bulk import and create hierarchy from CSV

[Santanu]

I'm trying to import CSV into our Jira and want to create a hierarchical issue list EPIC -> Story -> Task(SubTask).

I took the sample from 4) Import all other issues from the below link

https://confluence.atlassian.com/jirakb/how-to-import-issues-with-hierarchy-from-a-csv-into-jira-software-1087512458.html

Issue id	Parent	Parent summary	Summary	Issue Type	Status	Project key	Priority
1			EPIC Created - Ignore - Using API	Epic	To Do	INTERNALID	Medium
2	1	EPIC Created - Ignore - Using API	Assessment	Story	To Do	INTERNALID	Medium
3	2	Assessment	Project Kick-Off	Subtask	To Do	INTERNALID	Medium

I tried all different way to make it work and nothing worked. 

During the CSV import i'm using the below mapping :

What am I missing here? 

[Trudy Claspill · Accepted solution]

Hello @Santanu 

Welcome to the Atlassian community.

Are you trying to create issues in a Team Managed project or a Company Managed project?

For a Company Managed project, to import an Epic and a Story and have the Story become a child of the Epic you need to have a field/column in the Story row where that field is set to the Summary you used for the Epic, and you need to map that field/column to the Epic Link field. 

You should not be using the Parent column for identifying the Story's parent Epic.

One thing I am not clear on from your images is that the column headers in your table don't match the column headers that show up in the Mapping screen. The Mapping screen shows that there are columns for EPIC NAME and EPIC LINK, for example, but I don't see those in the table of sample data you provided.

[Santanu]

I'm not sure how to identify wherther it's Team managed or Company managed project. 

My bad , please look into the below table I was tying to import :

ID	PARENT ID	EPIC LINK	PARENT LINK	ISSUETYPE	SUMMARY	REPORTER	EPIC NAME
2			internal prokect Id	Epic	Epic One Summary, and a comma	internalid	Epic One
3		Epic One		Story	Story One	internalid
4	3			Subtask	Sub One	internalid
5	3			Subtask	Sub Two	internalid

Mapping was as below:

And validation failed with below message :

Your file statistics:

2 issue/s will be created correctly

0 issue/s will be created with warnings

2 issue/s will not be created due to errors

The validation process has found 2 error/s

• Subtask 'Sub One' doesn't have a valid Parent Id selection. Issue will not be created.
• Subtask 'Sub Two' doesn't have a valid Parent Id selection. Issue will not be created.

[Trudy Claspill]

When you are in Jira viewing the project look at the bottom of the navigation panel on the left. That is where it will say 'team-managed' or 'company-managed'.

To get your subtasks created under their parent Story you need to map your Parent ID column to the Parent ID field.

[Santanu]

Thanks .

The Jira project I'm working on is Team Managed. Does that make any difference?

Also as suggested I re-import the same CSV file with below mapping : 

And got the below validation error: 

I moved ahead and imported to get below result, Story was not added as a child

[Trudy Claspill]

It does make a difference that the destination project is Team Managed.

Using CSV import it is not possible to import issues and make them children of Epics during the import process. This problem is documented here:

https://jira.atlassian.com/browse/JSWCLOUD-17758

I have not recently tried to import issues with subtasks into a Team Managed project. I'll have to get back to you on whether or not that is possible.

[Santanu]

Thanks @Trudy Claspill 

[Trudy Claspill]

I was able to create new Stories and child Subtask issues in a Team Managed Software project using the External System Import / CSV option available to Jira Administrators.

Below is a sample of the CSV data I used.

Issue ID	Parent ID	Issue Type	Summary
8		Story	Story Summary
9	8	Sub-task	Subtask Summary

In the Field Mapping screen I mapped:

Column Name	Jira Field Name
Issue ID	Issue ID
Parent ID	Parent ID
Issue Type	Issue Type
Summary	Summary

All of the Jira Fields were under the "Issue Fields" heading.

I could also create Epic issues, but as I mentioned it doesn't appear to be possible to link child stories to their parent epics through CSV import.

[Santanu]

@Trudy Claspill  - Thanks a lot. I also tried , got the validation error but decided to proceed and it did work. I also tried to put the EPIC Id as Parent Id for the Story which didn't work. I can live with that. Again thanks and appreciate your help.

[Ditte Simard]

Hey @Santanu !

Despite what the article says, I would recommend that you separate the issues into 3 different CSVs: one for Epics, one for Stories, and one for Sub-Tasks.  If you have any new Stories that are supposed to be linked to the new Epics, make sure you import the Epic file first and then update the Epic Links in the Story file.  That should fix some of your problems.

Also, make sure you are taking into account any mandatory fields.  The import won't work if you are not filling them out in your import files.

I hope this helps!

[Santanu]

Thanks @Ditte Simard , 

I have another way to achive the same , Jira API, which requires tons of coding. If atlassian is demanding this can be achived through CSV import, I expect someone will stand behind to support that.