Issue Key Reset

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

7 answers

1 accepted

1 votes

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)

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.


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

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


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!


Thanks for all of your answers, much appriciated.

0 votes

    This thread is a bit old but this KB is new and may help someone.

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


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,089 views 13 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot