CSV Import Error: Project key invalid although this is correct in CSV

[Radu Ichim]

Hello,

I'm currently migrating some values in a project, from an older custom field to a new one, using the CSV export-import. I exported the tickets from this very project, including the Project key/Project name fields. Now, when trying to import the file (Import to Project -> Defined in CSV), I get the following error once mapping the fields:

"Invalid project key DAM: Project key or name is already used. If you want to import to an existing project the name and the key must match it exactly."

What can be the issue here? I did this a couple of times already for other projects and it all worked perfectly.

Any input is welcome.

Thanks!

[Rilwan Ahmed]

Hi @Radu Ichim ,

May be there is a mistake in mapping. In the csv file, use only Issue key, summary and the required fields only and uncheck "Use an existing configuration file". In the next screens, select the required project for mapping and do the column --> Field mappings manually. 

For example: If you want to update the Resolution field, the have only Issue key, summary , Resolution columns in the CSV import file. 

To update existing issues, your CSV file needs to contain a column that maps to Issue Key. If an issue exists for a given key, it will be updated.

Please note: Always try with single issue import and if it is successful, continue bulk import. 

More details in https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/