Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

My newly create jira issues have a massive number for an identifier!?

Christian Weaves February 23, 2021

I started with Jira 5 and have subsequently upgraded over the years to Jira 8.  Originally newly created issues were create fine in terms of a project/issue key (ISSUE-1, ISSUE-2, ISSUE3 etc etc).  Somewhere along the line these sequential numbering has gone a miss, newly created issues now are in the hundreds of thousands (ISSUE-240104, ISSUE-240105 etc), Jira works as expected but some how and I have no idea how 240,000 has been added to my numbering sequence. It would be nice if I could some how subtract this 240,000 and the system generate the next issue number with somthing that is a little easier to convey in spoken conversation!

Thanks 

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Champion
February 23, 2021

Hello @Christian Weaves 

With JIRA Server it is possible to change the next number to be used for a new issue in a project by updating the database. If you do a search in google for "jira server reset next issue key number" you will find a few posts on that topic from this community.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 27, 2021

Bear in mind that if you do this, it will crash when the numbers hit an issue that already exists

I would move the high-numbered issues out to another project before changing the number on the project. (see the project table in the database)

I would also want to find out where the emoty numbers are coming from, or there's every chance it will happen again.  The usual culprit I've seen is an incoming email with broken characters in it - the mail handler sees it, reads it starts to create an issue (hence "reserving" the number), then craps out and doesn't create or delete/mark read the email, so the next time it runs, it does it again.

Christian Weaves March 3, 2021

So I went along with Trudy's suggestion (before your post @Nic Brough -Adaptavist- ). I updated the next Id in the database and added a few issues. When my pcounter naturally incremented to an id that already existed it appeared to jump to the next available id. As a result I'm confused.  I have just over 200 issues until I hit my next "reserved Id" so I'm in two minds whether to leave it or not!?!

Thanks

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2021

You really need to find out what is causing the increments.  Have you got any mail set up for this?

Christian Weaves March 9, 2021

Sry for delay. No, no mail ingestion. Really not sure how it got in this state.  Might be related to various upgrade processes (5 to 8 over the years). 

Thanks for getting back to me.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events