nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue Bulk Importing, how do I import the epic Link?

John_8g0jxe

I have a csv file that I am using to bulk import issues. All of the columns/data are translating without issue except for the "Epic Link" Field.

I have an Epic with the Epic Link "Test Epic". I have a column in my csv file called "Epic Link" and the relevant rows have the value "Test Epic".

When I bulk import my issues this value is not populated and it doesn't generate an error. I have tried with and without quotes. Any ideas?

Thanks

Accepted answers

All comments

Trudy P Claspill

Are you importing the issues to a Company Managed project or a Team Managed project?

For a Team Managed project it is currently not possible to use the CSV import to link stories to Epics.

For a Company Managed project, if the Epic already exists in Jira and you know its Issue Key (i.e. ABC-123), add that key to a column in your CSV for each child issue, and link that column to the Epic Link field when mapping fields for your import.

If you are trying to create the Epic in the same CSV import process as the child issue, then you have to do something like this:

Type,Issue ID, Summary, Epic Link
Epic, 1, Epic Summary,
Story, 2, Story 2 Summary, 1
Story, 3, Story 3 Summary, 1
Story, 4, Story 4 summary, 1

Create an Issue ID field in your CSV. Assign unique numbers in that column to each issue. For the child issues, put the Issue ID value of the parent Epic in the Epic Link column for those child issues. When importing the data, again map that Epic Link column to the Epic Link field.

John_8g0jxe

Thanks,

This is for a company managed project. The epic does already exist within Jira.

So in the current epic link column I have, I can just replace the name "Test Epic" name I currently have with the issue key of the epic and that will work?

Mayur Jadhav_30osel

Hi @John

I have already provided answer for the similar question, would request you to check this too.!!!

csv import: import to issue under epic

Please let me knw in case of any queries or questions.

Regards,
Mayur

Trudy P Claspill

Yes, it should.

Daniel Miradakis

Can confirm, as of 2022-09-13, you still cannot link new issues to Epics when importing issues for a Team-managed project.

Trudy P Claspill

You can vote/comment on Atlassian's backlog issue about that here:

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

Sierra_f2eqyc

Hi @Trudy P Claspill would you please review what I have and point me in the right direction?

I'm trying to follow these directions of yours:

"If you are trying to create the Epic in the same CSV import process as the child issue, then you have to do something like this:

Type,Issue ID, Summary, Epic Link
Epic, 1, Epic Summary,
Story, 2, Story 2 Summary, 1
Story, 3, Story 3 Summary, 1
Story, 4, Story 4 summary, 1

Did I misunderstand something?

Trudy P Claspill

Hello @Sierra

Are you a Jira Administrator?

Are you working with Jira Cloud or Jira Server/Data Center?

How did you access the CSV import functionality? There are multiple ways to get to it.

- from the Advanced Issue Search screen

- from the Create Issue dialog

- for a Jira Administrator, from the gear icon / System / External System Import

Sierra_f2eqyc

@Trudy P Claspill yes I am. Jira Cloud. I accessed it by clicking "Import issues from CSV" within the software project on the Issues tab.

Trudy P Claspill

Try the Jira Administrator path:

from the gear icon / System / External System Import / CSV

Tomislav Tobijas

🗓️ Tested this on 15/7/2023.

Conclusion

⛔ While relation Issue Id ↔︎ Parent Id works for linking sub-tasks, it doesn't work for linking issues with Epics
✅ Linking issues with Epics works if you set ⚠️ unique Epic Name value and then use that same value for Tasks/Stories in Epic Link column.
When talking about a "unique" value, this means that this value must not already exist in your project, nor you can use the same value/string more than once in your .csv file

For example, you can use value "Epic #1" for Epic Link if there is/will be only one Epic with Epic Name "Epic #1" within the project where you're importing issues.
It seems that within the same instance/site, you can have multiple Epics with the same Epic Name, but they would need to be in different projects than the one to which you're importing new issues.

Even though "Epic Name" field is not required (since a few weeks ago), it seems that it's the only way to link issues with Epics. If anyone knows a better solution for this, feel free to share the knowledge. 🙌

*import was tested via Jira admin section (Settings > System > External System Import)

tabish.mohammed

This helped me importing similar issues in different epics in JIRA.

Thank you for your help on this! :-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

import

atl-gruland

bulk-edit