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

[Siva Kumar]

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!

[Siva Kumar]

I'm not getting epic link option, that's the problem. Please refer to my first screenshot, I edited my content. I want to know how to get epic link and epic name.

[Nic Brough -Adaptavist-]

Does your import contain only issue level issue types?  (No Epics or sub-task types)

[Siva Kumar]

Scenario 1 :

Issue Type	Epic Name	Summary	Epic Link
Epic	Epic Name	E summary
Story		Ssummary1	Epic Name
Story		Ssummary2	Epic Name
Task		T summary	Epic Name

Scenario 2 :

Issue Type	Epic Name	Summary	Epic Link
Story		Ssummary1	Epic Name
Story		Ssummary2	Epic Name
Task		T summary	Epic Name

Second scenario, if my Epic "Epic Name" already exists in Jira.

Here is my problem, I am not getting Epic Name and Epic Link fields to map while mapping before validation and import. Please refer my screenshots w.r.t custom field configuration, hope I'm clear. Please let me know if I need to provide more details.

PS: I'm not an administrator!! But I can ask him as per your guidance!!

Thank you :)

[Nic Brough -Adaptavist-]

So, to simplify a bit, use scenario 2 only (drop the Epic issue type line for now) and then remove the column "epic name" completely.

Next, check what type of issue "task" is - a lot of people have that type as a sub-task type.  If it is a sub-task type, remove that from the import as well.

Now, when you try to import this with the project import, you should find Epic link works fine.

One other last thing though - can you also check that your Epic link column contains the exact Epic Name that is on the pre-existing Epic as plain text - NOT the summary of the Epic.

[Siva Kumar]

Dear Nic,

So, to simplify a bit, use scenario 2 only (drop the Epic issue type line for now) and then remove the column "epic name" completely. --> Scenario 2 I am not mapping or importing that Epic Name field, if there is no Epic then there is no Epic Name, just an example, I thought it may give a better understanding, I used that column, there's no data in that I can remove that column. 

Next, check what type of issue "task" is - a lot of people have that type as a sub-task type.  If it is a sub-task type, remove that from the import as well. --> No, my Task is not a Sub-task. My story and task belong to the same Hierarchy. My Sub-Tasks are different CSV files I import using the Parent ID.

Now, when you try to import this with the project import, you should find Epic link works fine. --> This is the problem I'm trying to ask from the beginning. I'm not finding Epic Link and Epic Name fields in the drop-down Jira Fields(custom fields) list during import procedure. What configurations I need to enable them.

One other last thing though - can you also check that your Epic link column contains the exact Epic Name that is on the pre-existing Epic as plain text - NOT the summary of the Epic. --> Yes, I am using Epic Name and Epic Link fields to map Epic with respective Stories and Tasks, not sub-Tasks!! 

Thank you, Siva K.

[Nic Brough -Adaptavist-]

Ok, thanks for testing/clarifying all of that.

The only other thing I can think of is that the epic link field is not even valid for the issues you are trying to import. 

This will only happen if you've removed the field from the project somehow (as a locked field, you should not be able to do this on Cloud, although you could hide it or remove it from screens, which should not actually affect the import)

Simple test - click "create" and try to create a new issue in the project you are trying to import the issues into.  Are you offered the "epic link" field?  (remember to check "where's my field" to find out where it's gone if it is not given to you)

[John Funk]

@Siva Kumar  - I assume you got this figured out?