How to Reset Issue Key Numbers in Jira Cloud?

[Purnendu Chavan]

Hi,

I am using Jira Cloud and would like to reset the issue key numbers for a project. Currently, the issue keys are in the format PROJ-101, PROJ-102, and I want them to start again from PROJ-1.

Is it possible to reset or reconfigure the issue key numbering in Jira Cloud? If not, are there any workarounds or best practices to achieve this?

Any guidance from the community would be greatly appreciated. Thank you!

[John Funk]

Hi Purnendu,

It is not possible to reset issue key numbers for a project in Jira Cloud. 

Here is the request if you would like to vote for and follow it. 

https://jira.atlassian.com/browse/JRACLOUD-34286

The workaround right now would be to create a new project.

[Trudy Claspill]

Adding to this...

Why do you want to reset the numbering? What problem are you trying to solve?

Issue numbering starts at 1 in a project by default. If the issues are currently being numbered 101 and greater then one might conclude that the numbers smaller than 101 have already been used. An issue key can't be used for more than one issue. If an issue with the key PROJ-1 currently or previously existed the you can't re-use that key.

If you explain the problem you are trying to solve, then perhaps we can address that.

[Gregg Reaves]

@Trudy Claspill @John Funk I actually have a use case for this - I'm in the middle of a JPD migration and don't have a sandbox to test external importing (I REALLY wish atlassian would include JPD in the data migration tool.... pretty please?)

I don't want to mess with the current ticket ids, so as a workaround I tried some test imports with a forced ID of TICKET-90000000 not considering that the project would see that as the highest value and continue upwards from there

so now our tickets go from IDs of TICKET-1491 and the next ticket is TICKET-90000021, so I want to clear all that out and get things back consistent without having to create a new project.. because you can't reuse a project key so it's just a hassle to have to redo alot of automations, filters, and such to account for a different project key, I'd like to get the project back reset so it starts back at 1492 and not 90 million 22

does that make sense? do I have any options besides recreating and disrupting our current reporting and automation setup?