Update existing issues by loading the CSV file in Jira Cloud

[Natalia Golikova]

Hello!

I saw many discussions and videos on how to do the bulk update of the existing issues by loading the CSV file.

It creates new issues even if I map the issue id.

I don't have an option in the dropdown menu to map the issue Key.

So, I tried issue ID instead of issue Key and it creates new issues instead of updating the existing. 

Is there a solution for this problem?

I need to update about 800 issues.

Thanks,

Natalia

About the same discussion, but it didn't work for me:

https://community.atlassian.com/t5/Jira-questions/Whether-Jira-supports-updating-existing-issues-using-CSV-import/qaq-p/1008434

[Fernando Eugênio da Silva]

@Natalia Golikova 

As mentioned, you need to have a column with Key of the issues and map this column for the Issue Key field when you're mapping your CSV file. Also, the Summary field needs to be present and mapped in your CSV.

Please, try again and let us know if need more help

Kind Regards,

Fernando

[Pramodh M]

Hi @Natalia Golikova 

Issue key should appear when you are importing issues from the admin page.

Hope you are importing the issues by navigating to System and then External System Import.

[John Funk]

This is what you need to try.

[ROBERT]

Hi  Natalia Golikova

Im havving the same problems, im unable to update the issues using csv, insted is creating new ttks. 

It seems all tutorial form 2023, Kira didnt have the issue ID option, insted they where using isse KEY.

But the ISSUE KEY option doesnt apper on the field to be selected  :( 

[Natalia Golikova]

@Fernando Eugênio da Silva @Pramodh M 

Thanks for you answers.

Yes, I followed those recommendations, but I don't have key option.

I tried the same using IssueID instead of Key, but it creates new issues instead of updating the existing.

Another problem is that if I don't include issue type into CSV I receive an error and Jira thinks that my issues are sub-tasks, but they are not. 

Is it a Jira bug?

Here are the screenshots: 

Step 1 - CSV file

Step 2 - Loading the CSV

Step 3 - Setting the project

Step 4 - Mapping the fields

No Key option!

If searching "issue" - Issue ID is available. I created a different CSV file with Issue ID instead of Key and it didn't help.

Next screen to map the values:

Step 5 - Validation

Error

This is another problem. If I include issuetype column into CSV then there is no error and Jira created new issues. it happens with both files with mapping IssueID and with Key which I cannot map due to no option in dropdown menu.

[Fernando Eugênio da Silva]

@Natalia Golikova , thanks for sharing all details.

Could you confirm the steps you're taken to go to import csv screen? Generally the steps are: Go to System > Select External System Import. Is this the way you're doing?

All other steps it seems ok and you should be able to do the import without more problems.

[Hannes Obweger - JXL for Jira]

Hi @Natalia Golikova

I trust that Fernando's answer helps with the CSV import!

Just in case that you'd prefer a more interactive experience and are open to solutions from the Atlassian Marketplace, you may also want to have a quick look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. All editable fields can also be updated in bulk, via copy/paste. This works within JXL, but also between JXL and pretty much any other app, like so:

As you can see, this is super flexible - you really just want to pay attention that you are pasting into the right set of issues. This works for any number of issues in one go, so you should be done with your work in no time.

I should also add that JXL can do much more than the above: From support for configurable issue hierarchies, to issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes