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; } } }

Importing CSV File - Issue Key in Dropdown Does Not Appear

Deven_8s9jon

Hey all.

I was importing a few test tickets in Jira from CSV files. I'm trying to set the issue key value to a specific value within Jira, but when I try to map the Issue Key to Issue Key, the only two dropdown menu options I have are Issue Type and Issue ID. I tried two browsers, Vivaldi and Firefox, but I'm not able to map the issue key in my project management workspace.

Here's the article I was following:

https://support.atlassian.com/jira/kb/set-jira-project-issue-key-counter-to-a-custom-starting-number/

I saw in the image that Issue Key is mapped to Issue Key. But like I said, that dropdown option doesn't appear. Could I have assistance?

Accepted answers

Trudy P Claspill

Hello @Deven

There has been a terminology change that has not reached all documentation yet. Issues are now called Work Items.

Map to Work Item Key instead.

All comments

Martin Runge

Hi @Deven

If you're using the "Import issues from CSV" option in a particular project's sidebar, please note that you won't be able to map the Issue Key there. To access the mapping option, you'll need to use the Global External System Import tool with Administrator rights.

Deven_8s9jon

Ok. The good news is I am an admin.

This is my first time accessing Global External System Import tool. Is this outside of Jira or is this within Jira cloud?

Deven_8s9jon

I just found it.

Deven_8s9jon

It appears I'm still unable to set the Key when going to Settings>System>Import and Export>External System Import. It's completely grayed out and when going to the next page, it doesn't show up with the issue key.

Trudy P Claspill

Hello @Deven

There has been a terminology change that has not reached all documentation yet. Issues are now called Work Items.

Map to Work Item Key instead.

Trudy P Claspill

And you need to first click the option for Switch to the old experience

M Chandra Shekar

@Trudy P Claspill I agree with your explaination. @Deven We will be able to see work item key only not issue key in global import.

Deven_8s9jon

@Trudy P Claspill I didn't see an option to switch to the old experience. I did find Issue Key after selecting UTF-ACSII. I'm attempting to map the Issue ID to the Issue Key.

The problem, now, is that the import page is stuck on a hung, spinning session on Mapping Data to Your Space. I'm not trying to map a space, though. Just a ticket so that I can set the issue key number to a custom number.

Deven_8s9jon

Anyone else got a solution? I'm not finding anything.

M Chandra Shekar

Hi @Deven @Are you trying to import via Jira filters project level or Global external system import ?

Deven_8s9jon

Hey Chandra,

My goal is to change the number of a work item key. This is because my original ticketing system didn't start off in Jira. I was using another ticketing system.

I'm starting off with test tickets, but I eventually want to learn how to set an incident ticket to a specific number. I attached an example of what I'm looking for.

From my understanding, I'm supposed to upload a CSV file to change the value. I've tried this a few times and couldn't figure out how to make this work. Any assistance is appreciated.

M Chandra Shekar

@Deven Jira doesn’t allow changing issue keys number after creation. It is a unique identifier automatically generated by Jira when a ticket is created.

Piotr -Mederak Apps-

Hi,

if the real goal is to preserve the old FreshDesk reference, I would avoid trying to force Jira issue keys to match the old system.

A safer pattern is:

1. create a custom field such as “Original FreshDesk ID”,
2. import the old ticket number into that field,
3. let Jira generate its own Work Item Key,
4. use the custom field for searching, reporting and traceability.

That keeps the historical reference without fighting Jira’s key generation rules.

Full disclosure: I built Excel Backlog Importer for Jira. For this kind of migration-style backlog handover, the app can help when the source is an Excel workbook: map columns like old ticket ID, summary, description, priority, etc. into Jira fields, validate rows, and preview what will be created or updated before anything changes in Jira.

It will not rewrite existing Jira issue keys, and I would not recommend trying to use it for that. But for controlled mapping of old external IDs into Jira fields, this is exactly the kind of use case where a reviewed Excel import can be safer than manual CSV cleanup.

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