How do I update existing issues using the CSV importer for JIRA OnDemand

The Importing Data from CSV - Atlassian OnDemand Documentation reads:

Updating existing issues

From version 4.3 of JIRA Importers plugin you can update existing issues. Your CSV file needs to contain a column that during the import wizard is mapped to Issue Key. If an issue exists for a given key it will be updated.

I have tried this and there is no Issue Key to map to.

2 answers

1 accepted

3 votes
Accepted answer

I have have found a workaround. Under JIRA Administration > System. Under IMPORT & EXPORT > External System Import select Import from Comma-separated Values (CSV). This wizard includes the 'Issue Key' in the field selection dropdown.

Thanx - Very helpful input! This should be implemented in the official Atlassian support documentation

Hi, Thanks! Been looking everywhere for a resolution to this. My problem was using the "Import Issues from CSV" option from the issues drop down, this does not have the Issue Key field as an option. Didn't bank on there being different import options from different menus! Thanks for the workaround!

Note that CSV import for users in Issues > Import Issues from CSV is limited to creating issues as per its respective documentation in is for the administrator as you can see the page location in the page tree on left-side. 

Hi Thanks for the information. The documentation says updating of the existing issues from JIRA version 4.3 and above. Would like to know is there any difference for the cloud versions of Jira.

Hi, I am actually using the steps above BUT by mapping the Issue Key and Summary I am getting an error that the issue already exists! it's not updating

I am using the External System Import

I see the same thing as Shalvika Sood Anyone know why this is happening?  Did the update functionality get deprecated?  I am using v6.2.6#6264-sha1:ee76422

0 votes

Eh? Look at one of the issues you want to update. The issue key is now on the screen in front of you next to the summary and it's in the URL as well. The bit that says project-number (JRA-123 or whatever)

Nic, I have identified the keys of the issues I want to update and they are listed in the CSV file but there is no option to map to them in the import wizard. There is no JIRA field for Issue Key.

Hi, did you ever get to the bottom of this? I'm having the same problem!

He was looking at the user importer which only allows for "create" and hence doesn't need issue keys He's solved it by using the Jira Importer which supports updates when given an existing issue key

Oh, that was badly written. By "user importer" and "Jira importer", I mean there are now two CSV importers available. The user importer is available to normal users, but the Jira importer is for admins only.

Ah, I made the same mistake. I've found it, thanks!

@Robert Jacobs2  Where have you found 'admin' importer? Can you please specify it step by step? Having problems with it.. 


thank you!

  • to access admin importer

    Log in to JIRA as a user with the JIRA Administrators global permission.
    Select Administration > System > Import & Export > External System Import.

@Eugene Yasyuchenko as @vitaliy zapolskyy pointed out the location of the Admin External Import. Just remember if you are updating that the importer requires a summary field however the summary does not need to be mapped (leave it unchecked). As long as the issue key exists, it will update those tickets. 


I'm getting below information while i try to update the existing issues in Jira with new values.

"while updating issues have been skipped because they already exist in destination projects."


Please let me know why i get this error. I'm Jira administrator. Below are the steps i follow:

In Jira settings --> System --> Import and Export --> External System Import --> 

1. I get Jira Import wizard

2. I selected CSV

3. I got new page as CSV file import. Here i have File import and i uploaded the CSV file which i prepared. (Note issue key and all details are available. My aim is to change the Story points in each issues to a new value in Jira using this bulk option)

4. I map in the next page "Fields" only the Issue key and Story points.

Output is what is mentioned in the first line.

Request to guide me in steps (micro level) so that it can benefit everyone.

Thanks in advance

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Jira

Meet the Jira Software 8.0 platform release

  Hello Atlassian community!   We're excited to share the Jira Server and Data Center 8.0 platform release.  With 8.0, teams will be able to work more productively and sca...

789 views 15 12
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you