Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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 NameEpic LinkParent IdIssue IdIssue TypeSummaryDue DateStart Date
Contract Transfers   EpicContract Transfers1/31/20223/2/2022
 Contract Transfers 101TaskCopier Contracts12/15/20211/14/2022
  1011011Sub-task Identify/Validate list of copiers by division9/1/202110/1/2021
  1011012Sub-task Work with Ricoh to transfer billing12/15/20211/14/2022
 Contract Transfers 102TaskData Circuit Contracts11/1/202112/1/2021
  1021021Sub-task Identify/Validate list of data circuits9/1/202110/1/2021
  1021022Sub-task Contact Carrier to request change of owner form10/1/202110/31/2021
  1021023Sub-task Submit owner change form to carriers11/1/202112/1/2021
 Contract Transfers 103TaskRing Central account12/15/20211/14/2022
  1031031Sub-task Discuss transition of configuration to QUES account9/1/202110/1/2021
  1031032Sub-task Engage Ring Central to assist with moves9/15/202110/15/2021
  1031033Sub-task Review and sign RC SOW10/1/202110/31/2021
  1031034Sub-task Complete transition of RC accounts12/15/20211/14/2022
 Contract Transfers 104TaskSecurity Systems12/15/20211/14/2022
  1041041Sub-task TotalConnect Security Systems10/1/202110/31/2021
  1041042Sub-task Create new contract and account with Total Connect12/1/202112/31/2021
  1041043Sub-task Migrate services to new contract12/15/20211/14/2022
 Contract Transfers 105TaskMobile Solutions12/15/20211/14/2022
  1051051Sub-task Identify mobile devices that need to be transitioned12/1/202112/31/2021
  1051052Sub-task Have Mobile Solutions create a new bucket11/1/202112/1/2021
  1051053Sub-task Submit list of phone numbers to M.S. to move12/15/20211/14/2022
 Contract Transfers 199TaskPost Transition Cleanup/Validation1/31/20223/2/2022
  1991991Sub-task Validate transition of Mobile Solutions accounts1/31/20223/2/2022
  1991992Sub-task Validate billing of Security Systems1/31/20223/2/2022
  1991993Sub-task Validate billing of Ring Central account1/31/20223/2/2022
  1991994Sub-task Validate billing of Data circuits1/31/20223/2/2022
  1991995Sub-task Validate billing of copiers1/31/20223/2/2022
Active Directory   EpicActive Directory1/31/20223/2/2022
 Active Directory 201TaskAD OU Structure8/31/20219/30/2021
  2012011Sub-task Contact  IT for OU Architecture8/1/20218/31/2021
  2012012Sub-task Define dual OU Architecture8/15/20219/14/2021
  2012013Sub-task build out OU Architecture8/31/20219/30/2021

2 answers

1 accepted

1 vote
Answer accepted
Rachel Wright Community Leader Jun 29, 2021

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.

epic-import.png

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:

Hope this helps!

Rachel Wright
Author, Jira Strategy Admin Workbook

1 vote
Rachel Wright Community Leader Jun 24, 2021

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.

import12.png

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

@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?

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

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

Screenshot 2021-09-12 at 14.22.34.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you