We have encountered an issue with the sequence of our JIRA issue keys. Typically, the issue keys increase sequentially, but we observed an unexpected jump in the sequence.
Here is the detailed description of the problem:
When creating issues in JIRA, the issue keys normally increase sequentially. However, after creating the issue with the key "ISSUE-44," the next issue created had the key "ISSUE-55." There was a gap of several days between these two issues. This gap is not related to the issue, but I wanted to mention it. Regardless of the gap, whenever an issue was created, other developers always cloned my issues.
We are curious if this cloning behavior could be causing the issue key sequence to skip, or if there might be another reason.
Could you please provide insight into why this issue might be occurring? Additionally, we would appreciate any guidance on how to prevent such sequence skips in the future.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.