Import data to existing Jira Project using a CSV file with the new Importer

[Patrick Alexander]

Hi there,

Atlassian is rolling out a new Importer for external Systeme. This one was also used for importing Issues to existing Projects in the past.

It seems that this option will no removed and you can only import complete projects that you have to create in the importer.

Does anyone know more about it?

https://support.atlassian.com/jira-software-cloud/docs/import-data-to-a-software-project-using-a-csv-file/

[Michiel Schuijer]

Indeed, the new importer still can't import issues into an existing project, for some odd reason.

Use the 'old experience' when you need to import issues from a CSV into an existing project. 

Last week and this week, we are having some issues with the old importer though, running subsequent CSV imports into the same project would break the relations, when using parent-child (parent/issue id) relationships in the CSV files. When you do multiple uploads of CSVs into the same project, make sure to use unique IDs, so not the same in separate files.

[John Funk]

I just imported issues yesterday and it ran fine with parent child creations. 

[Michiel Schuijer]

But did you run consecutive uploads into the same project? That was the scenario that did not work for us.

Example:

CSV-file1 has issues with parent-child relations, say 10 is parent for 11

CSV-file2 has (different) issues with parent-child relations, say 10 is parent for 11, and suddenly this updates unrelated issues from CSV-file1.

[John Funk]

If you run the second CSV file after the parent has been created, the second CSV file should reference the key of the parent issue created in the first CSV import. That would be a separate column in the second CSV for the Parent field. 

[Michiel Schuijer]

Sorry John, you're simply missing my points completely.

Each file has its own parent-child relations, and don't reference the issues in the other files, and don't need to refer to the key of the others.

My point is, that in the past, running consecutive imports into the same project were not conflicting with existing issues, but now they are, in our production instance anyway. Atlassian support is looking into to it.

I tried to be informative here, in case anyone else ran into this.

[Patrick Alexander]

Thanks for the replies.

I hope, this option will stay there... or the now importer gets the same features ;)

[Marc - Devoteam]

Hi @Patrick Alexander 

You can still switch to the old importer, an use it.

This can only be done via the admin option in the System section, there you can still do an external system import, buy switching to the old importer.

This will be there for a while as if you want to import in JSM projects, only the old importer can be used.

[John Funk]

Hi Patrick,

You can still use the old importer.