Why ticket number ID's are skipping in Project?

[Charlotte Bish]

We have a Software Project in Jira which when you go to 'create a new ticket' but then discard i.e. do not submit the creation, it still seems to count the ticket ID as used somewhere in the backend. 

i.e. - I go to create a new ticket (lets say it should be ID-30 based on next numeric ticket) but then discard the ticket. Then I go to create a new ticket and do complete it, I will then see ID-31 and ID-29. The initiated but discarded ID-30 is taken but not searchable? 

We do not see this with other Jira Software projects and wondered if someone can help understand what setting may be doing this?  

[Tom Lister]

Hi

This is a database behaviour. The issue creation is taking the next available number in a sequence. If you then don't complete the process the id cannot be returned.

This is common practice but arguably this could/should be done as late as possible in the issue creation. But this doesn't appear to be the case.

[Charlotte Bish]

Do you know if this is this something we are able to control? Just seems odd that it occurs with this one particular project in Jira.
Other projects only assign the ID once a ticket/issue is officially 'created'.

[Tom Lister]

Are the other projects the same type?

team managed vs company managed?

[Charlotte Bish]

Yes, both company managed - software projects

[Tom Lister]

I tried to recreate this on a cloud test server and couldn't.

Have you any other feature in this project? Scripting, behaviours?

[Tom Lister]

maybe one for Atlassian support?