How can I populate/enable custom fields to Map which are required for CSV import?

Siva Kumar_9s96ot

Dear Atlassian Community,

I'm trying to import Epics and their stories from CSV, to link Epic's to respective stories I'm not finding Custom fields Epic Link and Epic Name to map(my first screen shot). Below, I'm sharing my configuration details of my custom fields, requesting you please look into it and guide me.

 While importing issues through csv, Epic Name and Epic Link are must exist to connect the stories with respective epics.

In my case they are available to map in Jira.

Please help me, How can I fix this.

Thank you.

Siva K.

 

Nic Brough -Adaptavist-

These two fields are odd ones, they represent a link between and Epic and its issues, and they rely on each other.

What happens is that an Epic has the Epic Name set, and you link issues into it by using the Epic Name in the Epic link on the issue.

Epics are issues in Jira, but have some extra functions.  They must have an Epic name (which is annoying, when you've already got a summary which would probably be even more useful to use as the linking), and they can not have Epic links, because they can't be part of another Epic.

You may find it easier to split your import into two - one for all the Epics, where you populate Epic name, then all the other issues with their Epic links set.  Note that if you do a single file, you won't be able to specify the Epic link to any imported Epics because they won't exist until after the import!