How to recover a deleted work item in Jira Cloud

First: is it really deleted?

Before anything else, rule out the two things that look like a deletion but are not.

• It was moved. Search for the old key, for example key = ABC-123, or paste the old link. A moved work item redirects to its new key in another space.
• It was archived. On Premium and Enterprise plans, archived work items disappear from boards and searches. A Jira admin can find them in the archived work items list and restore them.

If the search for the key returns nothing at all, the item was deleted.

Why Jira cannot bring it back

Deleting a single work item in Jira Cloud is permanent. There is no trash or recycle bin for it, and no undo. Whole spaces (projects) go to a trash for 60 days, but single items do not. Atlassian's own feature request for a recycle bin, JRACLOUD-36415, has been open since 2014.

A backup does not solve it either. Restoring a Jira Cloud backup replaces the whole site, so everything that changed since the backup would be lost to recover one item. Atlassian Support cannot pull one work item out of a backup for you.

Where the content usually still exists

1. Email notifications. The reporter, the assignee and every watcher got an email for the creation and for each comment. Search your mailbox for the key: you often get back the description and most of the comments, word for word.
2. Links from elsewhere. Confluence pages, other work items, pull requests and chat messages that mentioned the key often quote the important parts.
3. Exports and reports. A CSV export, a dashboard screenshot or a sprint report from before the deletion can give you the fields.
4. A backup file, read by hand. If your admin keeps backup exports, the data is inside. You cannot import one item from it, but you can copy the text out.

Whatever you recover, you will be creating a new work item with a new key. Add a comment with the old key, so anyone who searches for it, or follows an old link, can find the new one.

Who deleted it?

Depending on your plan, a Jira admin may find the deletion in the audit log (Jira settings, then System, then Audit log), or an organization admin in the organization's audit log. If not, the short list is whoever holds the Delete work items permission in that space: check the space's permission scheme.

Stop it happening again

The reliable fix is permissions. In the space settings, open the permission scheme and remove Delete work items from roles such as Member, so only administrators can delete. A permission scheme is often shared by many spaces, so copy it first if only one space should change.

Then give people a way to close an item without deleting it: a resolution such as "Won't do" or "Duplicate", or archiving on Premium. Most deletions are someone tidying up, not someone wanting the history gone.

If you want an undo anyway

Permissions prevent most accidents, but not all of them: admins still delete, and bulk changes go wrong. For that, an app has to keep a copy of each item before it is deleted. No tool can recover an item it never saw, so this only helps from the day it is installed.

We make one: Restorable keeps a copy of each work item inside your own Jira site, lists what was deleted, and recreates an item in one click with its fields, status, links and quoted comments. Attached files cannot be restored (Jira deletes them), but the restored item lists each one. There are other apps that do something similar on the Atlassian Marketplace; whichever you choose, check what it restores and where it keeps your data.