Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,297,265
Community Members
 
Community Events
165
Community Groups

How Do I Link a New Task to an Existing Epic when doing a CSV Import?

I am importing some new tasks in to Jira via CSV and I want to be able to link them to an existing Epic while also blocking an existing User Story.

I have been able to successfully do a CSV import that creates the tasks with the values I want set and create the "blocks" link, but I am not able to get the import to create the link to the existing epic.

My CSV is set up as follows:

issuetype, epic link, summary, priority, assignee, reporter, link "blocks", original estimate

Task, XXX-404, New Task Description, Medium, Assignee1, Reporter1, XXX-460, 36000

XXX-404 is the key for the existing Epic.

XXX-460 is the key for the existing Jira to set up the blocked relationship.  

Everything is working except the creation of the link to the Epic.  The issues are being imported in to Jira successfully and no errors are being reported.

2 answers

1 accepted

2 votes
Answer accepted

Hello @KD 

Welcome to the community.

Are you importing into a Company Managed project or a Team Managed project?

If importing into a Company Managed project, then add a column named "Epic Link" to your CSV and in the column enter the issue key XXX-404. You will need to map that column to the "Epic Link" field when mapping other fields for the import. That should add the item as a child issue of the Epic XXX-404

Thanks Trudy, I am in a Team Managed project.  Any suggestions on how to make the link in a team managed project?

I don't think it is possible to link a new issue to an existing Epic in a Team Managed project using CSV import.

In Team Managed projects the Epic Issue Key is stored in the Parent field for its child stories, whereas in Company Managed projects it is stored in the Epic Link field.

In Company Managed projects the Parent field is used only in Sub-tasks to store the issue Key of the issue that is the parent of the sub-task.

Based on my experimentation with CSV import, when Parent is selected for the mapping field, the import process assumes that the issue being imported is a sub-task. If the Issue Type of the imported issue is not a sub-task issue type, then the import process reports this warning:

"Issue 'summary text doesn't have Subtask Issue Type, its Parent Id mapping will be ignored."

...and the imported issue is not added as a child of the Epic.

Like # people like this

Thanks Trudy, I've found some other info that also says the same, that it isn't possible in a Team Managed project which is too bad.  I've just added a label during the import for now and then go in and make the bulk change after which is an extra step but not horrible.  Thanks again for the help.

Like Fernando Candia likes this
0 votes

I'm facing this problem too in a team-managed-project.

The related issue is https://jira.atlassian.com/browse/JSWCLOUD-17758. I voted for it.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,658 views 37 46
Read article

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