Cannot update the existing issues via CSV Import

[Hannah]

Hi the Community,

I tried to update an existing issue via CSV import. Instead updating the existing issue, I got a new ticket created. Can someone please help me to review what went wrong?

1. access via Issues in the tool bar

2. map the issue key

3. It creates a new ticket with the log below.

[John Funk · Accepted solution]

Hi Hannah - Welcome to the Atlassian Community!

You should map to the Issue Key instead of the Issue ID. You can call it whatever you want in your CSV file, but it checks the Issue Key field to see if that value already exists and if it does then it does an update instead of a create. 

[Hannah]

It is unfortunately not possible to map with Issue Key. It's not available in the dropdown - not possible to add it neither.

[John Funk]

You should go through the Settings > System > External System Import path

Use the Switch to the old experience link. 

As you can see in my example, it shows up there.

[Hannah]

Hi John, thanks a lot, however I don't have the access to system and won't get it as I'm only a user :(

[John Funk]

Have your Jira Admin run it through then. That's the only path you can do Updates to existing issues. 

[Trudy Claspill]

Hello @Hannah 

Were you able to accomplish your requirement by working with a Jira Administrator for your instance? If so, please consider clicking the Accept Answer button above John's response to mark your Question as Solved.

[Sandhi Trivedi]

I am JIRA admin and Issue Key still does not show up for me. When I try to update existing issues

[John Funk]

Hi Sandhi - Welcome to the Atlassian Community!

Please post a new question to the Community with your specifics needs. 

[Radek Dostál]

You can't update existing issues from CSV as a non-admin.

What you're showing in ss is user-facing import, it does not support updating existing ones.

You'd have to get an admin to use the "admin-facing" csv import which supports it.

That's how it worked since I can remember, I'm not aware of that being changed.

Alternative (as a user) would be to do it with REST, but that's a different matter entirely.

[Hannah]

It's a whole different story then with Rest API...

[Vishal Biyani]

In JIRA cloud importing the issue is creating a new issue. 

Seems some functionality has changed as previously i think given an existing issue key and summary, we were able to update other fields.

[Hannah]

:(

[Trudy Claspill]

@Hannah 

You did not identify the type of Jira system you are using.

Are you using Jira Data Center or Jira Cloud?

What is your level of access for the system? Are you a Jira Administrator, a Project Administrator, or a non-admin user?

What value are you providing in your CSV for key? Does it match to the issue key of an issue that already exists in the Jira instance?

Do you have permission to edit the issue manually through the UI?

[Hannah]

• I think Jira Data Center.
• I'm non-admin user.
• The issue key is like JIRA-2301 and it exists already.
• I can edit the issue I want to update.