Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is there a way to restart unique numbering in a project when existing tickets have been deleted?

I have a project for Change Requests that relies on the unique reference number being the same as the legal document - someone accidentally added a bunch of records into this project interrupting the sequence. deleting the records did not return the missing numbers and there appears to be no way to restart the sequence even by changing the project key and starting from zero records.  


If anyone can help I would be most grateful.  

1 answer

1 accepted

1 vote
Answer accepted

Hi Anita, 

To my knowledge, there is no way of reusing ID's from deleted issues from the Admin interface.
The only option there might be, could possibly be in relation to the counter on the server-side of your instance, as discussed here:

However the label suggests you're on cloud, so this would not be an option for you.

If we know more about the case, perhaps there's something else that can be done so you won't rely on matching numbers in the issue ID's. 

What is the reason that the Change Requests and Legal Document have to have the same ID-number?

Many thanks for your answer Jakob,

I guessed as much about re-using issue IDs.  I did try to change the Project ID in the hope that it would restart the numbering sequence but to no avail.  You are correct that we are in the cloud version so no real opportunity to restart from the server side.  

In terms of making the numbers add up there is not really a problem other than it looks a bit odd - we are combining CRs from 2 sources (one share point list and one pre-existing Jira project that had not been particularly well used).  We wanted to keep the CRs themselves numbered in sequence so our respective accounting departments could keep in synch with the budget usage associated with each one.  Having successfully avoided using the same number twice it was a little disappointing to have to start in a shiny new project with Jira issue number CR-10 being associated to legal document number CR0018.   I bit the bullet and created a field called 'Original CR Reference' and typed in the original number.  I guess it would be nice to be able to reset the counter in future versions, in case someone else does something silly like I did.

Kind regards


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

241 views 7 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you