Hi Support,
Kindly required your support on restoring the deleted CR from the Jira. we have deleted only the child CR but parent CR also get deleted.
CR issue - Need to recover it
Hi @Gani Siddiqi ,
This is a community forum not Atlassian support, but we can give you help and advice.
Although in this case the advice might not be what you want to hear.
In Jira cloud, deleting a work item (issue) is permanent. It is completely removed from the database and doesn't go to a "recycle bin," meaning there is no native undo or restore feature.
In future all I can suggest is don't allow anyone to have the permission to delete work items, if they're not needed archive them instead.
Hi @Gani Siddiqi
There is no native option to recover a deleted work item from Jira.
By default there is no backup within Atlassian Cloud.
If you have a backup option in place, you could spin up a new cloud an import the backup.
Backup options:
Hi @Gani Siddiqi - As others have mentioned, once something is deleted in Jira it's gone permanently - there's no way to recover it. To prevent this kind of thing in the future, install a third party backup app like Rewind into your Jira and Confluence instances. (Disclosure I'm the founder of Rewind). Backup apps like Rewind take regular snapshots of your data so that if something is accidentally deleted, it can be restored (along with the associated child items).Unfortunately, backup apps only work *after* you install them - there's no way to retroactively go back and help you with this CR that you've lost.Happy to answer any questions if you have them.
Hi @Gani Siddiqi !
Unfortunately, Jira Cloud itself doesn't have a restore option that allows to easily recover the deleted issues. If the issues were deleted in Jira, you can either try to restore them from a backup or contact Atlassian support.
If you are considering the options to prevent such a situation in the future and are open to using third-party apps, I recommend using Issue History for Jira (Work Item History) app by SaaSJet.
Using this app, you'll be able to:
Track the complete Jira issue change history
Monitor deleted issues and restore them if needed
Export full historical data in Excel, CSV, or PDF formats
You can test this app whenever you want, as it is available on Atlassian Marketplace, and explore its capabilities.
Hope this helps you prevent such unpleasant situations in the future.
One thing worth checking first: in Jira admin > System > Audit log, search for "Deleted" to see exactly which keys were removed, by whom and when. Deleting a parent also deletes its sub-tasks, so the log will show whether the delete actually started from the parent. That tells you what to rebuild from a backup or from emails and notifications.
Disclosure: I'm the developer of RestorePulse. For next time, it keeps the last version of every issue and recreates deleted ones, comments included. When a parent and its sub-tasks go together, it reconnects them on restore. Limits: it works only for deletes made after installation, restored issues get a new key, and attachments are gone for good.
https://marketplace.atlassian.com/apps/2772215736/restorepulse-restore-deleted-issues-for-jira
In native Jira Cloud, deleting an issue (or Change Request) is a permanent database operation—there is no native recycle bin or undo button. For an issue that has already been deleted without a backup app installed, your only native recovery options are:
Settings > System > Audit log
To prevent accidental deletions from causing permanent data loss going forward, besides restricting the Delete Issues permission in your Project Permission Scheme, you can install Restore Deleted Issues (or the lighter Track Deleted Issues edition):
Sorry to hear that. As others said, Jira Cloud has no recycle bin, so a deleted work item can only come back from a backup.
To prevent it from happening again: in our implementations, the very first thing we do for every client is remove the “Delete work items” permission from everyone except org admins. Check this in every permission scheme, because by default it’s often granted to broad roles like Administrators or even all users. If people need to get rid of something, they close it with a resolution like “Won’t do” or “Duplicate” instead, so the history stays in place and you can always reopen it.
It looks like you're new here. Sign in or register to get started.