Why issue's keys increment randomly to high numbers?

[Bartosz Wojciechowski]

Hi,

I am using Jira Cloud Software. I've created a new project and when I am adding tasks, their keys increment randomly to a high number. So for example:

- I have created 4 sprints in Jira

- I have started adding a tasks in sprint 1

- The first task's key is AA-6

- The second task's key is AA-19

- The third task's key is AA-32

Do you know what is the reason for this? We have more projects in Jira and it is the first time that we see it.

[Jack Brickey · Accepted solution]

I note from your data that there is a delta of 12 between each. My theory is that there is some automation creating sub-tasks when you create an issue. As Leonard suggested first verify if there are indeed gaps.

[Bartosz Wojciechowski]

Thanks, after AA-32 it started working correctly. More details in my reply to Leonard's answer

[Leonard Chew · Accepted solution]

Check your issues by executing this query:

project = AA order by key asc

Might be that your boards dont show everything.

If there are "holes" in the numbers, it is most likely that the issues were deleted.

[Bartosz Wojciechowski]

This is a newly created project so I didn't delete anything yet.

I used the query proposed by Leonard and I can see the same issues as on the board.

I added few more tasks and after AA-32 incrementation works correctly so right now I have AA-32, AA-33, AA-34, AA-35. Maybe the problem was related to the four sprints that I've created in the backlog before creating the board.

Thank you for you answers.

[Leonard Chew]

Strange thing. Last thing to try: Type the key of a "missing" item in the search field (e.g. AA-7)

If it was moved to another project, then you will be redirected to the new key.

[Bartosz Wojciechowski]

Thank you! Now I can see that one of the previous project initially had a key AA and then was changed to AK. When I typed key of a missing item in the search filed it redirected me to another project.

[Leonard Chew]

Great thing this mystery is solved :-).

In the activity-history of the issue, you will see when the issue was moved by whom.