nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA ticket ID are skipping and do not run in sequential order

Sirada Fongratanakul

I had created a bug tracking project and it seems that when a new defect has been created the ticket ID tends to skip and not run in order. Also checked whether those missing tickets had been deleted, and no they have not been deleted.

Sequential Order:

Ticket-1, Ticket-2, Ticket-3, and so on.

In reality:

Ticket-1, Ticket-3, Ticket-6.

If anyone had encountered something similar or could share an idea I could look into would be great

Accepted answers

Valerie Knapp_dpp5c6

Hi @Sirada Fongratanakul , welcome to the community and thanks for your question.

Please can you give some more context to this question? When you refer to tickets and defects, are they the only issue types in the project? For example, if this is a JSM project, and you have other issue or request types, the other ID's are likely being consumed by the other ticket types being created. Apologies if I have misunderstood the question.

Perhaps you could share an anonymised screenshot for us to see a little better what is going on?

Cheers

John Funk

Hi Sirada - Welcome to the Atlassian Community!

What happens if you search for Ticket-4 in the search box?

I suspect they did actually get deleted, but you were not aware.

The other thing might be if you are using issue level security on the project and you just don't have access to the issue.

All comments

Valerie Knapp_dpp5c6

Hi @Sirada Fongratanakul , welcome to the community and thanks for your question.

Perhaps you could share an anonymised screenshot for us to see a little better what is going on?

Cheers

John Funk

Hi Sirada - Welcome to the Atlassian Community!

What happens if you search for Ticket-4 in the search box?

I suspect they did actually get deleted, but you were not aware.

The other thing might be if you are using issue level security on the project and you just don't have access to the issue.

Sirada Fongratanakul

Hey John,

Thanks for answering!

So if I were to search for the ticket number that had been skipped it would show as the image I've attached below. I did speak to the admin whether she could see the ticket or not and she seems to not have access as well. She also checked the audit log to see if there were any deleted tickets and found none.

John Funk

The audit log will not show the deleted tickets. I would check your permission scheme to see who has the permission to Delete Issues and tighten that up if you have not already.

But bottom line is that I have never seen Jira skip ticket numbers in hundreds of thousands of issues that I have been exposed to. I would say with a very high level of certainty that they were deleted at some point.

Sirada Fongratanakul

Hey Valerie,

Thanks for answering!

Sorry let me clarify the details. So this happened in a project with 3 issue types (defect, inquiry and request/task). I have attached the ticket number to show what I'm currently dealing with, as you can see the number had skipped from 104 to 111 and this seem to occur no relation to the issue type. Sorry I had to hide the key name.

Sirada Fongratanakul

Yes, I did check the permission and only the admin of this project has the permission to delete. So the admin has reached out to the support team to see whether they can help us out.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software-cloud