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 change the starting issue key number? I'm using JIRA ServiceDesk Cloud version.

Ed Koo

I'm creating a new project in ServiceDesk Cloud and want to know how to change the default starting number for the Issue Key number. Currently any new issues I create start incrementing from the default 1. (e.g., TS-1, TS-2). I want to know if I can change the default value to something else (like TS-10000, TS-10001)?

I can change the Issue key prefix but I don't see a way to change the number.

The reason for this request is that I'm migrating over from Salesforce to ServiceDesk Cloud. I have a huge set of old cases to import from SF which will collide with my issues unless I change my JIRA numbering system.

Thanks in advance!

Accepted answers

All comments

Joe Pitt

You can't. I suggest creating a field named Salesforce ID and populate it from the import and only put the field on the view screen. Then it can be searched on.

Ed Koo

Thanks Joe - so it clear we users cannot reset the counter ourselves.

I also logged a issue with Atlassian Support. Judging from their response, it appears that they have the ability to reset the value for us and are willing to do so. Still waiting for them to complete this but will update this thread once I see the result!

Ed Koo

The only way to change the default starting number (pcounter) for the issue key (in Service Desk Cloud) is to submit a ticket to Atlassian Support and have them make the change. I was able to change my value this way.

Couple of things to consider:

1. You will need to confirm that all existing issues in the sequence have been removed, as once the counter is reset, it will continue the sequence if a previous issue is detected. For example, if you have existing issues PK-123, PK-124, PK-125 and you wish to change the pcounter to 500, you will need to delete all the PK-12* issues. Otherwise even after the reset the counter will detect PK-125 and use PK-126 for the next issue.

2. You will need to give Atlassian Support access to your project so they can make the change.

Hope this helps!

Simon O_Brien_zrp9x3

The way that I achieve this is to import a record via CSV and specify the Key value in the CSV file. So if I want to set the start number to TS-1000 then I would import a record with a key value of TS-999, when I next create a new issue / record in JIRA it will assign it a value of TS-1000.

Once a record has been created in the front end you can delete the record you imported via CSV

Brent Nye_45q7d9

This worked for me on JSM Data Center. Thanks for the suggestion.

Jack Brickey

@Simon O_Brien , would you mind providing more detail on your solution? I was just running a quick test in Jira cloud and what's unable to accomplish this as there is no means of mapping the issue Key.

@Brent Nye , I see you are using Data Center, I wonder if it is different than cloud.

Mark Price_t56gq9

You can do this with CSV import, which lets you specify a Issue Key.. i.e. BLAH-1000

see https://confluence.atlassian.com/jirakb/how-to-set-the-starting-issue-number-for-a-project-318669643.html

Hari Shankar_a230kg

Direct answer is available here - https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/#Importing-your-CSV-file

unknown

This is a misleading answer. You cannot randomly start the Issue numbering sequence at 1000. The Issue key numbers are created sequentially, starting a 1 and this sequence is immutable.

The only way to start at 1000, would be to create 999 Issues, then delete them.

This is exactly what the Atlassian Support team will do for you, if requested, to achieve what is described in @Ed Koo 's answer.

Jack Brickey

Hi @[deleted], the method described in the linked post does in fact allow you to add issues starting at a specific number. Did it not work for you. I have not done this in a long time so maybe something has changed. I may try today if I have time.

unknown

Hello @Jack Brickey

There is a disconnect here between the intention of what the OP requested and what that article describes. The OP wanted to start the Issue key numbering at a particular number, then continue on from that number henceforth, forever after, IN ALL CONTEXTS.

Importing a CSV as an external data source and 'forcing' an incoming issue to have a particular key number works in that context and that context only. When anyone uses the GUI or the REST API to create an issue, it will be numbered from the next available from the set of numbers that hasn't already been used. The index maintained by Jira as to what number is next in the set cannot be universally reset or 'forced ahead' to a particular umber by importing via CSV as described in that article. I confirmed the same myself via this thread a week or so ago.

The method I describe to 'jump ahead' to issue #1,000, for all contexts, is simply expending the issue key numbers from 1 to 999, so in effect you're artificially advancing the index, The same would happen by using the GUI to mass create 999 issues in an empty project then immediately deleting them... the very next issue would be #1,000

Welcome!

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

Quick Links

Find more posts tagged with

issue

jira

cloud

jira-cloud

atl-gruland

key