• Jira issue numbers are not strictly increasing, sequential issue numbers
• In certain scenarios it is possible for issue create to fail and consume an issue number, so the next successfully created issue may have a number that is not sequential with the last created issue eg ISSUE-1234 and ISSUE-1236
• This feature suggestion is to change this behaviour so that issue numbers are guaranteed to start at 1, strictly be sequential and as such predictable.

Update 24 June 2022

Issue Summary

• On the issue create screen when we have a validator to check if the field value is empty and then display the validation message.
• if we keep the field blank and get a validation message and then fill/select the value in the field and create the ticket, then the issue key sequence is skipped by 1.
• Provide logs or an appropriate error message on the UI for the users to know when the number is skipped.

Steps to Reproduce

• Step 1: On the issue create screen, have a field validator check the empty field, and then display the validation message.
• Step 2: On create screen keep the field empty where the validation rule is added and click create to get a validation message.
• Step 3: On the same screen correct the validation error by adding details to the field and click create.
• Step 4: A ticket will be created by skipping the sequence by 1 count.

Expected Results:

A ticket should be created having the correct sequence issue key as per the last issue key. For example, if the last issue key was 78 then the next key should be 79.

Actual Results:

A ticket is created by skipping the issue key sequence. For example, if the last issue key was 78, and while creating the first time we got a validation message, and then we correct the error and create the ticket, the ticket is created with issue key 80 and not with 79.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available