Hi everyone,
in one of our Jira Service Management Cloud projects we’ve noticed that some issue keys appear to be missing from the sequence.
For example, we can see issues like ABC-3295 and ABC-3299, but there is no trace in the UI, notifications or filters of the intermediate keys (e.g. ABC-3296, ABC-3297, ABC-3298). There are no obvious gaps around those numbers, just this specific block.
We understand that Jira uses an internal per‑project counter and that issue keys are not reused, but we’d like to confirm the following specifically for JSM Cloud:
In what situations can an issue number be “consumed” or reserved by the system, but the corresponding issue never actually be created/visible to users?
(e.g. failed validations, failed post‑functions, timeouts, imports, automation or integration errors, etc.)
Are such gaps in the issue key sequence considered expected behaviour in Jira/JSM Cloud?
Is there any official Atlassian documentation or knowledge base article that explicitly explains or acknowledges this behaviour (gaps / non‑reused issue keys / internal project counter) that we can share with our end‑users?
We’d appreciate any official references or explanations from Atlassian or from others who have had the same experience on Jira Service Management Cloud.
Thanks!
Thank you for your question, please note that Jira does not skip issue keys, so the answer to where they are should be found in the following questions:
Hopefully this helps you answer your inquiry, if so, please vote for it as the answer to your question.
Kind regards,
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.