One of my tickets seems to be deleted and I am unable to retrieve. It is of high priority.
+ to all recommendations below
It's really worth checking if your ticket isn't moved to another project. For this aim, you can read a use case:
How many tickets were moved from one Jira project to another? [Use case]
If it's deleted, there is no way to recover the ticket except from the backup.
If you want to avoid losing tickets in the future, you can use a plugin like Issue History for Jira. My team has developed it with an option to find and restore deleted issues. It stores all deleted tickets only after it's activated.
Let me know if you have any questions.
Hi @Nilesh Gupta ,
Are you sure it is deleted and not for example moved to a different project or put an issue restriction on so you can't view it?
I'm sorry to say, but deleted issues are not retrievable.
I would advice to really restrict the delete issues permission to prevent this in the future, although that does not help you right now.
- Tessa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
By default, Jira does not track deleted issues and deleted issues are lost forever. To prevent it happening again, you can try Restore Deleted Issues app developed by our team. In order for this app to work, the app must have been installed before the issue is deleted.
After you install this app,
Below you can find an article about tracking and restoring deleted issues in Jira.
How to Track and Restore Your Deleted Issues in Jira
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry to hear you have deleted a ticket, unfortunately as @Ajay _view26_ @Joe Pitt, @Tessa Tuteleers have pointed out you can't do much at this point, unless you have backed up your data.
BTW - As part of Atlassian's Cloud Security Shared Responsibilities, it is your responsibility to back up your Jira data as a Administrator.
Most Jira cloud administrators are under the impression that moving to the cloud means they do not have to have a data backup & restore strategy in place.
Looking forward your options at hand are:
There are pro's & con's for each of the approaches and depends on your organizations risk appetite and data volume.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's too late now.
Do not delete issues. When you delete it is GONE. Hardly a week goes by without someone wanting to restore an issue. Deleting issues will come back and bite you when it is the most inconvenient. I suggest closing with a resolution value of Deleted anything you want to delete. I implement a special transition only the project lead can execute and it requires filling in a reason field from a select list (such as entered in error, OBE, Duplicate, Other) and explanation text.
Deleting issues destroys historical data. Missing issue numbers will eventually cause a question about what it was and why was it deleted even if it was done properly. Missing data always brings in the question of people hiding something that may have looked bad.
The only viable way to restore an issue is to create a new instance of JIRA and restore a backup that has the issues. Then export them to a csv file and import them to your production instance. You will lose the history.
None of my users have delete permission.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately JIRA doesn't allow to recover deleted issues. So unless you have backed up your projects you wont be able to retrieve
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.