nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I update using CSV in non admin Jira tool if Issue Key is not available for selection?

Eric Satterthwaite

I'm a project admin for several Jira projects on my company managed Cloud version of Jira. I do large amount of importing of new work ( i.e. issues) into my projects. In the past when I provided my issue key and summary, I was able bulk update existing work for various fields with no problem.

As of recently, when mapping the fields in the Jira Import tool, I no longer see the "Issue key" as a selectable field to map. As a result, I can't do my large volume of updates.

Is this functionality no longer available for project admins or is it only for the enterprise admins?

Is there additional security profile permissions to allow me to do this?

Is there work around? We have a limited number of admins supporting 2000 user, so they don't have the capacity to run my csv updates.

Any thoughts or recommendations would be greatly appreciated.

CSV Problem.jpg

Accepted answers

All comments

Trudy P Claspill

Hello @Eric Satterthwaite

Welcome to the Atlassian community.

I did not think that non-admins could do that previously, but if you say you could I won't argue.

There was a recent change to rebrand "issue" as "work item". In the field mapping list you now need to use the Work Item Key field instead of the Issue Key field.

Eric Satterthwaite

Thanks Trudy, Work item is on the list either.

Trudy P Claspill

Based on my experience the ability to map to the Issue Key field was available only to Jira Administrators and you would only see it if you accessed the original import functionality through Settings (the gear icon next to your avatar) > System > External System Import.

I don't do CSV imports very frequently so I can't even say when the last time was that I confirmed that was the only way to get to it.

David Nickell

It appears 1/2 dozen CSV importer issues have been reported at jira.atlassian.com in the past 2 days: https://jira.atlassian.com/issues/?jql=summary%20~%20csv%20ORDER%20BY%20created%20DESC%2C%20updated%20DESC

I'm not sure of this specific problem is in the mix, but I was able to recreate your observation(s) and I am an admin on my site.

Perhaps the Issue Id should be enough. You shouldn't be able to change the key; the ID will hopefully get you pointed to the correct item for updating.

Prachi Bolar

Thats right based on the new change from issue to work most of the mapping fields have haveen changed to work items in jira import

example issue id - work item id

Please check this : https://support.atlassian.com/jira/kb/permission-needed-for-csv-bulk-import-without-giving-org-admin-permissions-to-users/

Eric Satterthwaite

I agree. I have imported ( i.e. created thousands of records) but to not be able to update in the same manner is tough to digest. My enterprise admin said he would execute my bulk csv update to get me over my current situation but I need a long term solution.

Another note: My admin said providing the "Make bulk changes global permission for our projects" would create a risk for any field with a set drop down list (Platform1 Platform 2, Platform 3, etc...) to have missing items added to the drop down list automatically if they are imported.

If the above is true then the import tool is inconsistent. When you import new records and if you had an invalid dropdown value in your file, the validation will display an error not add that record. Why wouldn't the same validation be done on global/enterprise dropdowns lists.

Thanks David for your feedback.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud