CSV Import Epic > Task > Subtask Next Gen project failing to link things together

[Jared Lindquist]

Using the data set below I'm unable to get epics, tasks, and subtasks linked together during import to a next gen board. I'm getting no warnings or errors and everything imports.

However:

1. I cannot see subtasks linked to tasks

2. I cannot see tasks linked to epics

3. and since subtasks are not linked to tasks i cannot see subtasks at all in the next gen board and only through filtering.

Very frustrating and time consuming if anyone can assist i would greatly appreciate it!

Epic Name	Epic Link	Parent Id	Issue Id	Issue Type	Summary	Due Date	Start Date
Contract Transfers				Epic	Contract Transfers	1/31/2022	3/2/2022
	Contract Transfers		101	Task	Copier Contracts	12/15/2021	1/14/2022
		101	1011	Sub-task	Identify/Validate list of copiers by division	9/1/2021	10/1/2021
		101	1012	Sub-task	Work with Ricoh to transfer billing	12/15/2021	1/14/2022
	Contract Transfers		102	Task	Data Circuit Contracts	11/1/2021	12/1/2021
		102	1021	Sub-task	Identify/Validate list of data circuits	9/1/2021	10/1/2021
		102	1022	Sub-task	Contact Carrier to request change of owner form	10/1/2021	10/31/2021
		102	1023	Sub-task	Submit owner change form to carriers	11/1/2021	12/1/2021
	Contract Transfers		103	Task	Ring Central account	12/15/2021	1/14/2022
		103	1031	Sub-task	Discuss transition of configuration to QUES account	9/1/2021	10/1/2021
		103	1032	Sub-task	Engage Ring Central to assist with moves	9/15/2021	10/15/2021
		103	1033	Sub-task	Review and sign RC SOW	10/1/2021	10/31/2021
		103	1034	Sub-task	Complete transition of RC accounts	12/15/2021	1/14/2022
	Contract Transfers		104	Task	Security Systems	12/15/2021	1/14/2022
		104	1041	Sub-task	TotalConnect Security Systems	10/1/2021	10/31/2021
		104	1042	Sub-task	Create new contract and account with Total Connect	12/1/2021	12/31/2021
		104	1043	Sub-task	Migrate services to new contract	12/15/2021	1/14/2022
	Contract Transfers		105	Task	Mobile Solutions	12/15/2021	1/14/2022
		105	1051	Sub-task	Identify mobile devices that need to be transitioned	12/1/2021	12/31/2021
		105	1052	Sub-task	Have Mobile Solutions create a new bucket	11/1/2021	12/1/2021
		105	1053	Sub-task	Submit list of phone numbers to M.S. to move	12/15/2021	1/14/2022
	Contract Transfers		199	Task	Post Transition Cleanup/Validation	1/31/2022	3/2/2022
		199	1991	Sub-task	Validate transition of Mobile Solutions accounts	1/31/2022	3/2/2022
		199	1992	Sub-task	Validate billing of Security Systems	1/31/2022	3/2/2022
		199	1993	Sub-task	Validate billing of Ring Central account	1/31/2022	3/2/2022
		199	1994	Sub-task	Validate billing of Data circuits	1/31/2022	3/2/2022
		199	1995	Sub-task	Validate billing of copiers	1/31/2022	3/2/2022
Active Directory				Epic	Active Directory	1/31/2022	3/2/2022
	Active Directory		201	Task	AD OU Structure	8/31/2021	9/30/2021
		201	2011	Sub-task	Contact  IT for OU Architecture	8/1/2021	8/31/2021
		201	2012	Sub-task	Define dual OU Architecture	8/15/2021	9/14/2021
		201	2013	Sub-task	build out OU Architecture	8/31/2021	9/30/2021

[Rachel Wright · Accepted solution]

Hi again @Jared Lindquist ,

The format you supplied in your table above looks correct. I wonder if "Contract Transfers" and "Active Directory" already exist as epic names in your application?  Were there any errors returned by the importer or in the "detailed log" file supplied by the importer?

During my tests, (it only took me 6 tries to get it working, LOL) I noticed that sometimes there was no error nor was an epic link relationship actually established. 

The example below works for me in Jira Cloud with a Classic/Company-managed project however.

Here's the format to use for the Epic and parent (Story, Task, etc.) relationship.

Image explanation:

• In the example Epic called “Company Rebrand”, I’ve given the row a Epic name of “rebrand” and left the “Epic Link” field blank.
  
  • The "Epic Name" field only applies to Epic issue types.
• Then, for each parent issue, I’ve added the name "rebrand" to the "Epic Link" field.
  
  • The "Epic Link" field only applies to parent issue types, like Task/Story/Bug, etc.

Tips:

• Here's a great thread with lots of good insights: https://community.atlassian.com/t5/Jira-questions/How-to-import-stories-linked-to-epics-in-jira/qaq-p/373117 including:
  
  • Make the selected Epic Name value unique (both for all epics in the import file and all epics that already exist in Jira.)  
  • There's also a workaround for Jira Cloud Next-gen/Team-managed projects mentioned.

Hope this helps!

Rachel Wright
Author, Jira Strategy Admin Workbook

[Rachel Wright]

Hi @Jared Lindquist , I think the trouble is the way your "Issue ID" and "Parent ID" columns are structured.  In my example below, the "Issue ID" field for the Sub-tasks is purposely empty.  Try changing that in your CSV file and let us know if the parent/child linking works.

Image explanation:

• In the example task called “Build a house”, I’ve given the row an Issue ID of “3308” and left the “Parent ID” field blank.
  • 3308 is any random number.  It is not the issue key that will be assigned by Jira.  Jira will only use this information for the import.
• Then, for each sub-task, I’ve left the “Issue ID” field blank and added “3308” to the “Parent ID” field.
  • This associates the “Pour concrete foundation” and “Frame exterior walls” sub-tasks with the parent “Build a house” task.

Hope this helps!

Rachel Wright
Author, Jira Strategy Admin Workbook

[Jared Lindquist]

@Rachel Wright 

Hi Rachel, thanks so much for this. It worked very well for linking the tasks and subtasks but not the epics. Do you have any suggestions regarding that?

[Jared Lindquist]

@Rachel Wright or anyone else if you have any ideas it would be most appreciated. Thank you.

[Miguel Angel Reyes Botello]

Hi @Jared Lindquist this worked for me fine even though the validator said the sub-task would not be imported: