Issue with import from CSV

[Collista Lewingdon]

When I am trying to upload a spreadsheet it is not connecting the epics or the tasks, and will add the assignee. I have been trying by using the import examples that Atlassian provided and no real data yet, but I cannot figure out why the link up is not working. Below is the way the screenshot is set up. 

I am able to get the system to accept the spreadsheet and it allows me to map everything correctly.

However, once I start the import I get an error for import users and import issues. This can be seen below. 

This is some of the warning messages that  I get once it imports everything. 

Then when I go over to the project, everything is there but the epics are separate from all the tasks. 

[John Funk]

Hi @Collista Lewingdon  - Were you able to try those latest suggestions? Is this still open for you? 

[Cloudites Owner]

What jumps out to me is the same data for both epic link and name. Epic link is the id (key) used by the epic name.

Ex: 

Epic Link - E1

Epic Name - Event Preparation 

[Collista Lewingdon]

We are creating epics at the same time as the tasks. Therefore there is not an Epic Key yet, which is why the epic name is the same name in epic link and epic name. 

[Cloudites Owner]

Exactly, commit.

[Collista Lewingdon]

Sorry, I am highly confused my your answer. 

[Cloudites Owner]

The commit order for the transactions is important, see your error log showing the system doesn't know the Epic because the transactions have not fully committed to your instance, you have to keep in mind you're working within a distributed architecture. Break the import into two files, the first all the Epics and the rest of the transactions. Process the Epics first with a fully successful log then process the second with the correct Epic Link. 

You can also use automation rules and / or Google sheets sync to perform the same functions.