How do I map Epic names on csv import?

[Ekow Essel]

Reaching out with what I hope is an easy question. I'm trying to do a simple CSV import for tickets in upcoming sprints. When trying to map the Epics so I don't have to select "Add Epic" afterward, I'm finding difficulty. I've tried using Issue Key, Issue ID and Parent ID. My csv file headers are:

• Epic Name 
• Issue Type 
• Summary 
• Description 
• Labels 

They're all exact match, I just can't figure out what to include in the epic name header. I saw a similar post from 2020 about a bug, but I've got to imagine things have been fixed since then? Any suggestions here?

[Trudy Claspill]

Hello @Ekow Essel 

Welcome to the Atlassian community.

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

Currently it is not possible to set the parent Epic for a child issue if you are importing to a Team Managed project. That is noted in this issue:

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