JIRA next gen - how to import csv to update existing issues without creating new issues?

[Sarah Wood]

Issues already exist in the project.

I created an export of these issues, revised the values of some data and now want to import the csv to change the values of the existing issues.

Bulk update will not work bc there are different values for different issues.

How can I use import to update existing issues without creating new issues?

[Ignacio Pulgar]

A csv import will update existing issues if a column with issue keys is mapped to issuekey field.

Including the summary is also required, even if you are just updating instead of creating new issues.

Ensure all columns contain valid data for the fields you are going to map them to.

By following the import wizard till the end, you'll update issues as desired.

[Sarah Wood]

There is no "Issue Key" in the JIRA fields dropdown. See screenshot.

[Ignacio Pulgar]

May you try typing "Issue Key"?

[Sarah Wood]

Maybe I already tried that and nothing came up?

[Sarah Wood]

Anyway I already found my answer - next gen might only support through the import that the administrator can access. I was hoping next gen would be better. 

Here's the link that states it does not support.

https://community.atlassian.com/t5/Jira-questions/How-do-I-update-existing-issues-using-the-CSV-importer-for-JIRA/qaq-p/22870

Thanks Community Leader!

[Dario B]

@Sarah Wood ,

Please notice that you are referring to a thread from 2014. Updating issues from CSV without creating new ones is actually possible in Cloud as you can read in the last status update on the below Feature Request:

• [JRACLOUD-65502] Import from CSV to Jira does not update Resolved Date field

  This is now working in Cloud.

  Only, the resolution dates are not imported/updated from CSV if you do not import/update the Resolution field as well. 

  As per the "Is there a way to change the "Resolution Date" thread in the Atlassian Community, in order to update the resolution dates you need a CSV file with at least the below 4 fields:

  1. Issue Key
  2. Summary
  3. Resolution
  4. Resolved (to be mapped to "Date Resolved")

Only, this may not work for Next-Gen projects due to the below bug (or similar):

• [JRACLOUD-70949] CSV import will fail if Next-gen custom field is mapped

Now, I know the thread is quite old. However, can you kindly let me know if this is still needed so that, in case, I can test if it is working like for Classic projects?

Cheers,
Dario

[Piyush A (STR)]

Does update to tickets via CSV triggers email notification?

[Ignacio Pulgar]

Sorry for my short answer. It was not intended to sound rude. Answerring from the phone just trying to be helpful.

Kind regards

[Larry]

it does not seem to work as advertised.

[Dario B]

@Larry  Please notice you are commenting a thread from one year ago that was actually solved (see my reply from Sep 19, 2019) without providing any context on what is actually not working.

If you need help or if something is not working for you, I'd advise to create a new question explaining what you are trying to achieve and what is failing.