How can I establish a link between an epic and issues while importing a CSV file?

Juan Truncon
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 28, 2024

I've attempted to connect an existing epic within my project with the new issues I'm importing from my CSV file. In my file, there's a 'Parent' column containing the ID of the epic to be linked, and when I map it, I choose the 'Parent' field in Jira. However, I consistently encounter the same error: 'Unable to retrieve issue key for parent: CDS-194´.

I want to highlight that the type of issue I'm using is a custom one that I created. I'm not sure if this could be causing an issue and preventing me from establishing the link between the epic and the issue.

This is how my file looks:
WhatsApp Image 2024-02-28 at 10.41.30 AM.jpeg

 

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 28, 2024

Hello @Juan Truncon 

Welcome to the Atlassian community.

The native issue hierarchy in Jira is:

Epic
|-- standard level issues (i.e. Task, Bug, Story)
|-- subtask level issues

If you are using the Free or Standard subscriptions, that is the extent of the hierarchy. An Epic issue can't have another issue as its parent.

If you are using the Premium or Enterprise subscription, then it is possible to extend the issue hierarchy above the Epic level.

Are you using a Premium or Enterprise subscription? And if so, have you extended the issue hierarchy configuration in this screen?

https://<yourBaseUrl>/jira/settings/issues/issue-hierarchy

If you answered Yes to those last two questions, then you should be able to set the Parent field in the Epic to an issue that matches the issue type you specified in the Issue Type Hierarchy in the level directly above Epic.

The next thing to confirm is that the issue keys you have specified in your CSV already exist in Jira as issues.

And then my next question would be about how you are mapping your CSV columns to Jira fields when you are importing the CSV.

Suggest an answer

Log in or Sign up to answer