You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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.
I tried to recreate this on a cloud test server and couldn't.
Have you any other feature in this project? Scripting, behaviours?