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:
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?
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.
And you need to first click the option for Switch to the old experience
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill I agree with your explaination. @Deven We will be able to see work item key only not issue key in global import.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Deven
Is the import process still getting stuck on the Mapping Data page or did you get past that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To go back to what I stated earlier, my original ticketing system was not on Jira. I was using FreshDesk before.
I have important archived tickets in another place, so if I have something like INC028 in my archives and INC-28 in Jira, those two issues wouldn't be the same. That makes tracking confusing.
From the article I was referring to in my initial post, I was under the impression that changing the key number is possible. Is this not up-to-date? Or do I have to create an entirely new space to make this work.
My recommendation is that rather than trying to set the issue key you should instead create a custom field in the Jira issues into which you can insert the original item ID from FreshDesk.
With a CSV you can set an issue key but you cannot change the issue key of an issue that already exists.
For example, the highest number used in my project ACMKP is 11.
I can use a simple file like this to create a new work item in the project with a higher number - 15
This is the mapping I use.
And this is the result that it reports.
And the output of my filter.
The autonumbering of issues would assign "16" to the next issue created.
I have only used this method to do a single bump of the number. I have not used this method to create multiple issues with specific keys but theoretically that would be possible if the import is executed by a Jira Admin.
In the CSV file I would make sure that the items are listed in issue key order, ascending. Also make sure that the first number used is not within the range of numbers already used in the file.
If you need to import parent and child issues in the same file this could be problematic. Parent issues all need to be listed in the file before their child issues. If that doesn't align with the ascending order of the issue numbers, then you may not be able to accomplish your desired goal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill Ok, perfect. That answers my question. I'll try that.
What I found odd was even though my self-hosted account is an admin account, it wasn't giving me the work item key option. But I'll try another CSV file to see what happens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To get the work item key option you need to go through the External System Import option.
Click the gear icon near your avatar and select System.
Find and click on the External System Import option. You should see a screen like this.
Click the Switch to the old experience option, and proceed with your import.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Deven @Are you trying to import via Jira filters project level or Global external system import ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with @M Chandra Shekar
@Deven why do you need to set the numeric portion of the issue key? What problem are you trying to solve with that solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To go back to what I stated earlier, my original ticketing system was not on Jira. I was using FreshDesk before.
I have important archived tickets in another place, so if I have something like INC028 in my archives and INC-28 in Jira, those two issues wouldn't be the same. That makes tracking confusing.
From the article I was referring to in my initial post, I was under the impression that changing the key number is possible. Is this not up-to-date? Or do I have to create an entirely new space to make this work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.