Does Jira reuse issue numbers from deleted issues?

I am seeing an issue number in a project which should already have been issued in the recent past. For example, I created a bug today, the its assigned the issue number Project-1015.

That doesn't make sense, because the latest bug from the project is numbered Project-1037. I am expecting any new bugs to be numbered higher than Project-1037.

The only theory I have now is that in my case, someone deleted the bug which was numbered Project-1015, and so the next bug created gets that number again. Does Jira 4.1 work that way? If so, can I change it so it does not do that?

3 answers

0 votes

It doesn't work that way. However, someone can hack the number creation by resetting the project counter in database. Anyone did that?

Out of the box, JIRA doesn't reissue the keys.

No one did that to my knowledge. We are not dealing with a vanilla jira out of the box. It has been configured for a couple years, and the original admin is no longer around. Is it possible to configure jira to reissue those numbers when items are deleted, without hacking the project counter in the database like you mentioned? In other words, could it already be configured to reuse those numbers?

No configuration as far as I am aware. Possibly done using some plugins but can't say much without seeing your instance!

Nope, it definitely does not do that, ever. The only time it reuses a number is if you entirely delete a project and then create a new one with the same name.

You definitely have a plugin doing something, or someone/something fiddling with the database counter.

I have an instance of this also but in the ondemand instance, where an issue AA-123 was moved to a different project and became BB-456. BB-456 was then moved back and became AA-130, all acting as expected. But a different issue was moved and given key AA-123. I am able to view in activities the flow of the issues, and can see the number designation histories.

I think you need to look more closely at the histories - I don't think this has happened, unless Atlassian have made massive changes to the product in the latest release.

I am having this exact same issue

You have a plugin or (bad) user hacking your database and doing the wrong thing.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,407 views 15 19
Read article

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