Whether Jira supports updating existing issues using CSV import (Bulk).

[Satheesh Kumar Srinivasan]

Do i need confluence to support this action to be completed. Or else base Jira itself had the provision. Please advice

Can i update only specific fields alone rather updating once again all fields. So i can only specify required fields with separate comma to get this completed.

[Megan Moulton · Accepted solution]

Thank you for this forum thread! I found this and @Mykenna Cepek's answers and understand everyone's struggles. After trial and error, here are the exact steps I used to NOT recreate issues and instead update all issues when bulk updating fields via CSV

1. Create a custom search for the issues I want to update. In this case, I specified the project and that my field was not empty (project = TEST and source is not EMPTY)
2. Selected "show in detail view" to specify the fields I want to be updated
3. This will pull up all the tickets that match your query and let you select which fields you want (otherwise, you'll get everything). Select columns on the far left side. 
4. Uncheck ALL columns selected and instead select Summary, Key, and the fields you want to update. In my case, I am updating the custom field "source". You must have the summary and key field to UPDATE your tickets. Without both, you will create new tickets. 
   
5. Select done and review your new query to ensure everything is correct
6. Select Export at the bottom and choose CSV-Export
   
7. Open the excel file and make the corrections you want. Do not change the summary or key field. In my case, I updated all data in the "source" column and hit save
8. Go to System > External System Import
9. Select CSV
   
10. Choose your file and select next
    
11. Select your project and then next
    
12. On the next page, you choose what data from your CSV you want to import. 
    1. For "Key" choose the Jira field "Issue Key" Check the box
    2. For "Summary" select the Jira field "Summary" and check the box. 
    3. Then choose the fields you want to update, which ones will be imported. I am importing "source" so I make the field and select the check box. This is the only field that will have UPDATED data. If you skip the issue key, it will make new tickets.
    4. For any other categories you may have, and don't want to import, make the field "Don't map this field"
13. Confirm everything is correct and select "begin import"
14. Now all your issues will be updated.

Hope this helps!

[Mike McNamara]

Thanks, these instructions do work successfully. I did find that with my server instance a few minor differences apply to the exact wording, but the process is the same (i.e. did not need to go to detail view, and column selection is via a drop down on the right).

Export a CSV that includes the key and summary plus fields to change, update the CSV and import it back in via External System Import > CSV. Works in multiple tests.

Thanks Megan!

[Finn Rakow]

THIS works, even for multiple projects. Thanks!

[Erik Aaron Hansen]

The Jira field "Issue Key" is not present in the drop down list. :\ I'm not admin but I'm admin in the project I'm trying to do it for.

[Mike McNamara]

It is just called "Key" in the drop down of fields to display from a search. After export, the column heading is called "Issue key" in the CSV file. 

[Erik Aaron Hansen]

Unfortunately there's no 'key' either in the drop down list. I see an "Issue id" under Links and sub-tasks, but when I selected that it went ahead and created new issues anyway.

[Mike McNamara]

Maybe were talking about a different drop down. See attached. When doing Issues>Search for issues, click on the Columns button to drop down the list of columns (fields) to show in the search results. "Key" is there for me (JIRA 8.2.3). I am an admin, not sure if that would be a factor, to restrict who can select Key. I would not think so.

 

[Johnny Mon]

Here is a video recording of updating one Jira issue's multi-select custom field using Jira's CSV import feature (Jira Software version 8.20.9):

1. Search for related issues created for this ticket
2. Setup the columns for export to include the minimum
3. Export the results to a CSV file
4. Edit the CSV file to update only one issue, Bug Environment from empty selection to DEV & PROD
5. Import the CSV file
6. Saw the incorrect summary
1 project and 0 issues imported successfully!
The above statement is misleading. We did updated an issue.
7. Download the detailed log and reviewed it
The log incorrectly said only new items will be imported.
The log says "1 issues successfully created" but we did not create but updated the issue.
8. Download the configuration file and reviewed it.
9. Refresh the current search
10. verified there were no new issues created
11. saw the issue SP-24 was updated and has correct multi-values
12. Open SP-24 and double check the Bug Environment values are correct

What was missing in the video and we should check, is the History tab - it will show what has changed in by the import.

Basic Steps:

1) export the CSV with only the minimal required fields: Issue Key, Summary, Fields that needed an update

2) Modify the exported CSV file to update the field

3) Import it back to Jira

4) Check the log for Errors. 

5) The log content can be misleading, as shown in the recording, possibly saying new issues were created but really meant updated.  We can verify no new issues were created with a JQL query.

6) Check the issue's history to make sure the import is successful.  

** Test in non-prod first and backup your data!

[meepzorp]

Thanks, but what if we are not a system admin?

[Johnny Mon]

Welcome @meepzorp  to the Community!

We can use a third-party application in the Atlassian Market place that will perform CSV imports for non-admin users.  There are some that will do CSV imports but did not specify if it can be done by non-admin users - you'll have to contact their support team for the answer.

An application can implement for non-admin users of CSV import by calling Jira REST API that updates issues, with the issue data converted from CSV to JSON format. 

[Petter Gonçalves]

Hello Satheesh,

Can you confirm to us if you are using JIRA Server or Cloud?

JIRA itself already have the functionality to import/export issues using CSV format and properly update existing issues on your instance. Here are the steps to update issues on Cloud and some server versions:

1 - On JIRA application, click to search for issues to display the issue navigator page

2 - Define which issues you would like to update in the filter > Click to Export it:

P.S: You can define in the List view the columns (fields) you would like to export if you use the option Export Excel CSV (Current fields)

3 - Once you export your CSV file, use a spreadsheet software (Excel, LibreOffice, etc) to update the relevant columns (fields) in your issues. Keep the issue-key unchanged in order to map the changes to the existing issues in your JIRA when you import it

4 - After saving the CSV file changes, navigate to your JIRA Settings > System > External System Import and import your issues back to JIRA, mapping the issue-key and all the changed fields

For more information about CSV imports, check the documentation below:

Importing data from CSV

Let me know if this information helps.

[Miguel Koropecky]

Will this also work for google sheets?

[Jean-Christophe Chaulieu]

Hello Petter

Your solution doesn't match. No overwriting existing issues, but incremantally added Issues.

[Martin Kunst]

Same issue here. despite correct mapping, I'm trying to update! the existing issues, but instead of update, a new issue is created.

[Guillermo]

Same issue here - @Petter Gonçalves could you provide some further assistance?

[Marc Isikoff]

How is this answer accepted? It poses more questions than answers.

The short answer to the OP question is No.

You cannot use "Import Issues from CSV" to update existing issues because once your CSV file is examined to map each field, Issue Key will not be present to map to even if you have it in your CSV. Thus you will create all new issues.

My scenario for needing this functionality is: 1.3k issues get some replacement fields that are shorter in name (so they are taking up less horizontal space on an issue listing) - while we can make the request screen say anything, we wanted shorter field names. So now we are dividing the work, manually updating 50 a week by hand because CSV doesn't work and bulk update only works for static data (e.g., cannot be used to make a field = another field value).

And our company does not let us import CSV any other way and even if we went up on high to get them to do this we were advised of a 6-week SLA in which time our CSV would be ~35% bigger.

[Matthew Berzinskas]

This is not the correct answer (anymore at least).

[Maksim Smetannikov]

Yes, you can update any fields in existing issues using system import CSV.

To update fields in existing issues, the required fields are issueKey and Summary + the fields you want to update.
You will need to do CSV export first and then import.

System import is located here: System/External system Import/CSV.

Be careful - create a backup before this operation.

Thank!

[Mykenna Cepek]

More information specifically about updating existing tickets via admin import is available here:

• https://community.atlassian.com/t5/Jira-questions/Update-existing-issue-via-import/qaq-p/1291133
• https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

I just recently had to do this in Jira Cloud. I'm including a screenshot below showing the trivial field mapping I used, allowing me to update one field on a subtask.

Relevant tickets in the JAC would include:

• Extend JIM to UPDATE already imported issues (closed Aug 2018 as "obsolete")

• Allow to update existing issues in the non-admin CSV importer (closed Apr 2021 as "won't fix")

• update an existing subtask through CSV import (open since Sept 2016)

Bonus tip: if you have any multi-line text fields, and your CSV isn't importing them correctly into Excel, don't open Excel and then import the CSV. Instead double-click on the CSV file in File Explorer (or in the Finder on MacOS). Only then (apparently) will the multi-line fields be imported correctly.

[Lisa Woolcott]

Just what I needed - thank you!  Worked liked a charm :)

[p0cket0m]

It does not work at all. If you map the issue key, it tells you all existing issues have been skipped.

If you unmap the issue key, it tells you it won't start import because there are sub-tasks in the CSV???????????????????????

[Cesar mazzo balsan, Paulo [BR NON-J&J]]

Hello, I'm trying to do so, but with no success. First I cannot find the issuekey field to map, it is simply not there, so I'm using IssueID, then I validate the field and it passes the validation, but when I actually load the updates, they take no effect over the issue. Can you help me?

[george Joseph]

I believe you might be using the Issue -->Import Issues From CSV option to do the mapping. The Issuekey field is not available through this option. You will have to go through the JIRA Settings > System > External System Import option. You need to be a JIRA admin (Not just the JIRA Project admin) to use this option. You can check with your enterprise JIRA admin.

[natalia.lezhai]

It does not work, issues are not getting updated, but new issues are getting created instead. I mapped issue key, summary, status, none of that works.

[Martin Kunst]

Same issue here. despite correct mapping, I'm trying to update! the existing issues, but instead of update, a new issue is created.

[Guillermo]

Same here, I'm not getting the issues updated - nor created again neither actually.

The detailed log states the following:

```

2022-02-16 18:39:50,649 INFO - Import started by ug:1d6a7630-05e1-4615-8299-3c19271e1bf7 using com.atlassian.jira.plugins.importer.imports.csv.CsvDataBean
2022-02-16 18:39:50,769 INFO - ------------------------------
2022-02-16 18:39:50,769 INFO - Importing: Users
2022-02-16 18:39:50,769 INFO - ------------------------------
2022-02-16 18:39:50,769 INFO - Only new items will be imported
2022-02-16 18:39:50,773 INFO - 0 users associated with import. All of them imported as inactive, this can be changed after import in User Access step.
2022-02-16 18:39:50,773 INFO - ------------------------------
2022-02-16 18:39:50,773 INFO - Finished Importing : Users
2022-02-16 18:39:50,773 INFO - ------------------------------
2022-02-16 18:39:50,773 INFO - 0 users successfully created.
2022-02-16 18:39:50,777 INFO - Retrieving projects...
2022-02-16 18:39:50,793 INFO - Project ExternalProject{id='null', key='VP2', externalName='null', name='Vintra Platform', type='null', template='null'} exists and found correctly.
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - Importing: Versions
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - Only new items will be imported
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - Finished Importing : Versions
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - Importing: Components
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - Only new items will be imported
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,797 INFO - Finished Importing : Components
2022-02-16 18:39:50,797 INFO - ------------------------------
2022-02-16 18:39:50,804 INFO - Retrieving custom fields...
2022-02-16 18:39:50,812 INFO - ------------------------------
2022-02-16 18:39:50,812 INFO - Importing: Issues
2022-02-16 18:39:50,812 INFO - ------------------------------
2022-02-16 18:39:50,812 INFO - Only new items will be imported
2022-02-16 18:39:50,834 INFO - Importing issue: [externalId='autoid-5785989079765498454', summary='[Create Connector Wizard] Back button works (2)']
2022-02-16 18:39:50,939 INFO - 0 out of 1 issues successfully created
2022-02-16 18:39:50,943 INFO - ------------------------------
2022-02-16 18:39:50,943 INFO - Finished Importing : Issues
2022-02-16 18:39:50,943 INFO - ------------------------------
2022-02-16 18:39:50,950 INFO - ------------------------------
2022-02-16 18:39:50,950 INFO - Importing: Issue Links & Subtasks
2022-02-16 18:39:50,950 INFO - ------------------------------
2022-02-16 18:39:50,950 INFO - Only new items will be imported
2022-02-16 18:39:50,954 INFO - ------------------------------
2022-02-16 18:39:50,954 INFO - Finished Importing : Issue Links & Subtasks
2022-02-16 18:39:50,954 INFO - ------------------------------
2022-02-16 18:39:50,955 INFO - ------------------------------
2022-02-16 18:39:50,955 INFO - Importing: Issue remote links
2022-02-16 18:39:50,955 INFO - ------------------------------
2022-02-16 18:39:50,955 INFO - Only new items will be imported
2022-02-16 18:39:50,959 INFO - ------------------------------
2022-02-16 18:39:50,959 INFO - Finished Importing : Issue remote links
2022-02-16 18:39:50,959 INFO - ------------------------------

And the issue's resolution date is not updated.

could anyone that got it to work give us some more insights?

[Mykenna Cepek]

Review the answer I offered in this thread on 30-Dec-2021. Lots of good information there.

[Guillermo]

Thanks, I just found the solution to my problem: updating Resolution Date per csv bulk is done only if the csv also includes the Resolution field along with the date.

More info -> https://jira.atlassian.com/browse/JRACLOUD-65502

[Anil Kathane]

Thanks Petter Gonçalves; the solution worked quite well for me. Thanks for providing the solution, much appreciate it.

Those who are facing any difficulties or those who have new issues getting created; please ensure you export the JIRA KEY when exporting; and map that field correctly to JIRA KEY when importing. This way JIRA would be able to map the issues and will update the records for the fields that you select while uploading.

Note: I am using JIRA cloud.

[Marc Isikoff]

Again, these "solutions" are are typically out of reach.

Either they are for Jira Cloud or they need you to complete own and have unlimited rights for admin.

Most Fortune 50 companies do not work this way:

1. Jira Cloud is contrary to most cloud strategies as one or more cloud providers are picked, and Jira Server is more or less lifted and shifted to the company's choice of cloud providers - employees are confused with their Jira in "the cloud" but not being "Jira cloud" - and Atlassian needs to start understanding their offerings are not core business to Fortune 50 and therefore are not going to get them on Jira Cloud but rather Server in a cloud.

2. Also most Fortune 50 companies do not give Jira project workers like a Product Owner or Scrum Master the complete keys to administer their Jira project hence we cannot do external system CSV import without going thru a lengthy permission process.

So in short, while "a solution" may exist for this problem, it is not tenable for many of us who can only do Bulk Update, or Import Issues from CSV.

[Mykenna Cepek]

The large company I'm currently working for has a small team of Jira Admins who help with such requests. As a ScrumMaster with only Project and Board Admin privs, I partner with them when I need to access privs beyond what I can do.

[Anil Kathane]

Totally Agree with Marc Isikoff for the issue of the need of admin access. It should be possible for regular users to do this upload. The solution, while it works well for me, I agree that it doesn't really help much.

[Jean-Christophe Chaulieu]

It doesn't function:

Issue in Jira-cloud

[Mykenna Cepek]

That linked ticket is not related to what is being discussed here.