Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira skip one issue creation



Jira skip one issue key, im in the issue PCBK-41 and when i created a new one jira put PCBK-43. I never created the issue PCBK-42 and deleted.

Some idea??



1 answer

1 accepted

1 vote
Answer accepted

Could someone have moved PCBK-42 to another project?  Could it have been secured away from you so you can't see it (with an issue security level)?

I have reviewed all the projects and the pcbk-42 is not there.

Ok, so you checked that there's no security scheme in place.  What error message did you get from looking for https://<your jira base url>/browse/PCBK-42 ?

Ok, great, thank you.  And the issue security scheme?  Does the project have one?

Ok, great, that proves the issue was not moved or hidden, so it was either skipped or deleted.

I am not aware of a way to get Cloud to skip issue creation (On server there's a known problem with misconfigured email boxes or malicious email content that can cause non-creation with number increments, and you can inject post-functions that can cause it - usually someone trying to do validation in a post-function, which is completely the wrong thing to do)

To check deletion, there might be a record in the admin audit log telling you the issue was deleted, and by whom, but that depends on the settings and age of the action.  I would want to check the project permission scheme for who can delete issues and check with all of them as well.  (Then probably remove the permission entirely, so that no-one can make the mistake in the future)

It could, of course, be a bug or hiccup in Cloud as well, but unless you really are losing issues, I suspect it will be written off as transient or a mistaken delete.

This would need to go to Atlassian as a support request if you think it was a bug or glitch and you many have lost data.

Thank you very much for your help!

I'm going to contact cloud support.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events