How can I import issues that are linked to an Epic type issue using the CSV importer? I can successfully create an Epic type issue using the CSV importer but when I try to link an issue to it (by mapping the Epic Link field with the Epic Name of the epic), the importer creates the ticket but doesn't actually link it to the Epic.
Does something have to be enabled on the Admin side first to make this work?
@Malik Mangier I did it today and it is possible to import issues as Epics. You have to map it though in the `import system` as the last step.
@alicia_juste It's suposed to be like this but it is not implemented yet as https://jira.atlassian.com/browse/JSWCLOUD-17758 says.
I did not found a `nice and easy` way to do it.
You can find partial workaround here:
Did not try it.
I'm having this problem as well. I've properly mapped the "Epic Link" column in my CSV to the "Epic Link" field in Jira, and I've tried it three different ways: using the epic's issue key, using the epic's issue id, and using the epic's name. None of these work properly.
When I use the issue key, the import completes successfully with no errors, but the link is still not made between the story and the epic.
When I use the issue id, the import completes, but errors happen, saying the epic cannot be found.
When I use the epic name, the import completes successfully with no errors, but the link is still not made between the story and the epic.
Can we get an update on this, please?
You need 3 things to make this work consistently:
On import, relate the columns, especially: "ID" with "Issue id". Then it will work
I followed these instructions, but wasn't successful. I think I'm a little confused by step number 3.
Where does the column ID come from? What does it mean that it's unique for each "Epic, standard, subtask"? I tried creating a column called ID and just filing in 1, 2, 3 as a test, but still wasn't successful.
Can someone provide clarity? Thank you!
@Brad Whowelland @Nicole Foxworth
When you are creating and CSV file you have to assign an unique issue ID for each of the `issues` (all types). But this is just local assignment.
So if you have:
`Story 1, ID 1`
`Sub-Task 1, ID 2, Parent ID 1`
` Story 2, ID 3`
`Sub-Task 2, ID 4, Parent ID 3`
` Sub-Task 3, ID 5, Parent ID 3`
You will have 2 Stories with subtask, Story 1 has 1 task, and Story 2 has two tasks.
It's just an simplified example :)
And when you import the issues it will analyze your IDs but in JIRA it will be the next available ID. eg. myID-1 = TEST-234, myID-2 = TEST-235 etc.
Hope this helps
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events