Issue Key Reset

[Shane Poole]

Can I reset the Issue Key for a given project, so that it starts from xxx-1?

[Abdoulaye Kindy Diallo · Accepted solution]

Kindly check the below:

• https://confluence.atlassian.com/pages/viewpage.action?pageId=211649701
• https://answers.atlassian.com/questions/86819/reset-the-issue-sequence-to-0-in-jira-4-4-5

[Svante Gustafsson Björkegren]

I have used this procedure several times and it does the job!

(https://confluence.atlassian.com/pages/viewpage.action?pageId=211649701)

But I usually discourage my customers to do this because I think that when you have to rely on what number an issue gets your process is wrong. That should be totally irrelevant because you will always end up with special cases to maintain this requirement. Better to take that off the table from start.

I have come across one use-case when I thought it was relevant though. I had a customer with a incident reporting system in Excel (common case ;-) and the existing incidents were already given id's in a sequence. They wanted to migrate this to JIRA without changing the numbering (there were many references to these reports in other systems)

When we had created the JIRA project and tried all the scenarios the pcounter was 134. If we would have imported the spread-sheet at this time the numbering would not have been preserved. So we deleted all test-issues in the project and followed the procedure described in the documentation and when we imported the spread-sheet all existing incidents reports got their correct numbering and all refereces were intact.

In conclusion: If you have built-in values in the numbering in your JIRA project, try to remove that requirement and see the key for what it is, a unique identifier without any value. This is a more maintainable and less complex approach.

If you have specific reasons (e.g. historical) you can move on with the procedure to reset the counter, just make sure you delete all issues in the project before and that you re-start your instance afterwards.

My 2 cents to this topic!

//Svante

[Nic Brough -Adaptavist-]

To save you some reading.

No, you can't reset the key. Unless you delete the project completely and re-create it, or start mucking around in the database (delete all issues in the project, stop Jira, backup, change the counter on the project table with a spot of SQL, restart it)

[rambabu patina]

We cannot reset the numbering through the user interface.

You can do it directly in the database. This particular SQL is relatively simple and safe compared with other things people make a mess of with SQL - you set the pcounter on each project you need to reset in the "projects" table.

Steps:

Stop the jira --> Take database backup --> run the sql --> Reindex the jira.

[Jan Szczepanski]

Hi all,

actually you can reset the project key when using scriptrunner. Here is the snippet, but be careful when using it ;)

https://bitbucket.org/janszczepanski/workspace/snippets/oBkRLy

[Eric Sebian]

now you're scaring me. What is there to be careful about? Entering the wrong key?

[Michael Dennis]

Unfortunately there does NOT seem like a way to do this for JIRA Cloud 

[Marlene Vitale]

Really would love to be able to do this. Can Jira from their end reset in cloud?

[Nic Brough -Adaptavist-]

In theory, yes, but I don't think they do it in practice. 

Raise a support request at https://support.atlassian.com/contact and see what the response is.

[michal]

If you import single task from e.g. CSV using Settings / System / Import and Export - External System Import and you set your to be starting Key for the task, it will have it and counter will get reset.
Used on cloud Jira - works.

[Fernando Pinheiro Felizardo]

Thank you @michal ! This works!

[Udo Brand]

Take a look at:

https://confluence.atlassian.com/pages/viewpage.action?pageId=211649701

[Daniel Santos]

Hello,
    This thread is a bit old but this KB is new and may help someone.
    https://confluence.atlassian.com/display/JIRAKB/How+to+reset+the+project+counter+after+moving+issues

[Shane Poole]

Thanks for all of your answers, much appriciated.