CSV Import is not linking items to epics

[justin-oh]

I'm unable to create the link from a Story/Task/Bug/etc. to an Epic via the CSV import.

During import, I can see the appropriate fields (work item id, work type, etc.).

After import, all items (including Epics) get created. The Epic associations are missing but I can set them manually afterwards. Sub-tasks are associated to the correct parent items.

I even tried using the raw CSV from this page which I edited to only have Epics and below:

issue type,issue key,status,summary,issue id,parent
Epic,test-125,To Do,Epic with parent and no child story but 1 sub-task and parent Inititive,3,
Epic,test-126,To Do,This is an epic with 1 story and 1 bug as child issues mapped,4,
Story,test-127,To Do,Example story 1 Summary no child issue mapped,5,
Story,test-128,To Do,"Example story with 1 child sub-task mapped, and a parent epic is mapped",6,4
Bug,test-129,To Do,bug with 1 child sub-task ,106589,4
sub-task,test-130,To Do,subtask 1,7,6
sub-task,test-131,To Do,subtask 2,8,106589
sub-task,test-132,To Do,Subtask 3,9,3

I get the same kind of errors after trying to import the above CSV:

• Cannot add value [ Work item ] to CustomField [JPT-126] in Parent Link with summary 'Example story with 1 child sub-task mapped, and a parent epic is mapped'. Probably value was in incorrect format
• Cannot add value [ Work item ] to CustomField [JPT-126] in Parent Link with summary 'bug with 1 child sub-task'. Probably value was in incorrect format

I have no clue how to proceed with / debug this problem anymore.

[Trudy Claspill]

Hello @justin-oh 

Into what type of project/space are you trying to import the data; Company Managed or Team Managed, Software or Business or Service?

Please also show us the screen where you are mapping the CSV column headers to Jira fields.

[justin-oh]

I believe Team Managed and it's started using the "Scrum" template so probably Software?

I start off at the "old experience": /secure/admin/ExternalImport1.jspa.

I select CSV.

I select the simple CSV file that I mentioned in the question and click Next.

I select my project and click Next.

Here's the field mapping:

Note: I cannot select anything referred to as an "issue". Everything is referred to as "work item" or "work type".

Here are the errors I get at the end:

Finally, proof that the Epics get created but no parent association:

[Trudy Claspill]

Hello @justin-oh 

Thank you for that additional information.

As per the following it is not currently possible to create the Epic/Child link when using a CSV import to create items in a Team Managed Space.

https://jira.atlassian.com/browse/JRACLOUD-83172

The relationships have to be created manually after the import, or an alternate issue creation method needs to be explored, such as API use or perhaps an Automation Rule.

On a side note you can find your Space type in two ways.

1. You can go to the View All Spaces page and find the information in the Type column. 

2. You can click the ... next to the Space name in the navigation panel on the left and you will find the Type information at the bottom of the resultant pop-up.

[justin-oh]

Confirmed it was a Team-managed software type project.

However, I just tried creating a Company-managed software type project with the Scrum template and I have the exact same experience using the import. I use the same mappings. The same errors appear. All the work items are created but the Epics are not linked.

[Trudy Claspill]

Hello @justin-oh 

I have also tried to import Epics and child issues, in a single CSV file, into a Company Managed project and am getting the same types of errors.

I have tried a variety of changes in the CSV. I have simplified it to the minimum required info. I have tried having the child issues (story, bug) listed in the file before their parent epic. I tried a few other things too, but nothing has worked.

I think there may be a defect here. I have submitted a support request to Atlassian on this issue. I'll report back here what they say.

[Rik de Valk _Brainboss_]

Hi @justin-oh , 

I think you want to create completely new issues with this import, am I right? 

If so, try not to map the issue key while importing. If you use an issue key, it will try to update existing issues. 

Whenever you want to create new issues, you have to omit the issue-key column. 

Have a nice day. 

Rik 

[justin-oh]

I've tried without an issue key before.

I'm doing the import with no pre-existing work items so the keys would not map to anything. Even if there were existing items, it still wouldn't map to anything because the system creates entirely different keys based on the project/space code (in my case JPT for Jira Project Test).

Still, I'm using CSV directly from the documentation page. It should work.