DEV Community

Aleksander
Aleksander

Posted on

How to Recover a Deleted Jira Issue in Jira Cloud (2026): What Works and What Doesn't

#jira #atlassian #productivity #devops

Short answer: Jira Cloud has no recycle bin for work items (issues). Once a work item is deleted, Atlassian Support cannot bring it back. You can recover it only from something that already existed before the deletion: a backup, a notification email, an automation rule, or a Marketplace app that was installed and tracking the project. If none of those were in place, the work item is gone and has to be recreated by hand.

The rest of this article covers how to find out what was deleted, each recovery route and its limits, and what to set up today so the next deletion is recoverable. Everything here is for Jira Cloud and was checked against Atlassian's documentation in October 2026.

Why there is no undo

Deleting a work item in Jira Cloud is a hard delete. The fields, description, comments, worklogs, attachments, links and subtasks are removed together.

Jira does have a trash, but only for whole projects (spaces): a deleted project sits in the trash for 60 days and can be restored. Individual work items do not go there.

The request for a work item recycle bin, JRACLOUD-36415, has been open since January 2014. As of October 2026 it has 706 votes and the status "Under Consideration". In 2020 Atlassian said it had no plans to support a trash for individual work items "for the foreseeable future".

Atlassian's own knowledge base article on the topic, updated in September 2026, is direct about it: "Atlassian backups can't restore individual deleted work items."

Step 1: Find out what was deleted, and by whom

Before trying to recover anything, confirm what happened.

  1. Go to Settings → System → Audit log. You need the Administer Jira global permission.
  2. Search for the event work item deleted, or type the work item key.

The audit log shows who deleted the item and when. It does not store the content, so you cannot restore from it.

Two limits to know about:

  • Deletion events have been in the audit log on all paid plans since February 2025. Sites where every Jira app is on the Free plan have no audit log.
  • Retention is configurable. If your site keeps audit events for a short period, an old deletion may already be gone from the log.

If someone ran a bulk delete, the audit log is also the fastest way to get the full list of affected keys.

Step 2: Recover the content

Every route below has the same condition: the source must have existed before the deletion.

Route What must already exist What you get back Main limit
Notification emails or Slack messages Watchers or a channel that received updates Whatever the messages contain Manual copy and paste
XML backup A backup file taken before the deletion Fields and comments, through a CSV export and import Slow, new key, needs a second site
Atlassian Backup and Restore The paid add-on, on Premium or Enterprise A whole-site restore Not for single work items; backups kept 30 days
Automation rule A rule that fires on "Work item deleted" The fields you chose to send Only what the rule captured
Marketplace app The app installed and tracking the project Fields, comments, sometimes worklogs and links Must be set up in advance

Rebuild from notifications

If the work item had watchers, their inboxes hold the creation email and every update. Search mail for the key. Slack or Teams channels connected to the project are another source. This is tedious, but for a single ticket it is often the quickest route.

Restore from an XML backup

This is the method in Atlassian's knowledge base:

  1. Take a backup file that was created before the deletion.
  2. Import it into a separate site. Importing a backup replaces the data on the site you import into, so do not import it into production.
  3. Find the work item on that site and export it to CSV.
  4. Import the CSV into your real site.

The imported work item gets a new key. Anything that referred to the old key, such as commits, links from other tools and bookmarks, will not point to it.

Atlassian Backup and Restore

Atlassian sells a Backup and Restore add-on for Jira, Jira Service Management and Confluence on Premium and Enterprise plans. Backups can be scheduled daily or weekly and are kept for 30 days. It is built for disaster recovery of a whole site or app. It does not restore one deleted work item into a live site.

An automation rule that captures deletions

Jira automation has a Work item deleted trigger. A rule with that trigger and a "Send email" or "Send Slack message" action can record the key, summary, description and other fields at the moment of deletion.

This does not restore anything by itself, but it gives you a copy of the content and an immediate alert. Test the rule on a throwaway ticket to see exactly which values arrive, and remember that it only helps for deletions that happen after you create it.

Marketplace apps

Several apps keep a copy of work items so they can be recreated after deletion. All of them work only for deletions that happen after the app is installed and configured. As of October 2026 the Atlassian Marketplace listings show:

  • Issue History for Jira (SaaSJet): a change-history and audit app that includes a recycle bin. Its documentation says it restores fields and comments, but not time tracking data or links, and that for attachments "only the name of the attachment is saved".
  • Restorify (Terano Apps): a dedicated restore app. Its documentation says it restores fields, comments, worklogs, links and subtasks, that tracking is off by default until an admin enables it per project, and that attachments are permanently lost.
  • Who Deleted My Issues? (Sevidev): logs deleted items and restores them, including comments and worklogs. The latest Cloud release on its listing is from June 2025.
  • Restore Deleted Issues (Bloompeak Labs): the most installed dedicated app. The latest release on its listing is from February 2024, and the listing does not carry the "Runs on Atlassian" badge. Atlassian ends support for the older Connect app framework on January 31, 2027, so check with the vendor about their plans before relying on it.

What you cannot get back

No route restores everything:

  • The original key. Jira does not reuse keys, so a restored work item always gets a new one.
  • Attachments. The files are deleted with the work item. None of the apps above documents restoring them.
  • The change history. A recreated work item starts a new history.

How to prevent the next one

  1. Restrict the "Delete issues" permission. This is Atlassian's first recommendation. In most projects only admins need it. Check your permission schemes, and check team-managed projects separately because their roles are configured per project.
  2. Close instead of delete. Use a status such as Canceled or Won't Do, or a resolution, for work that should disappear from boards.
  3. Archive instead of delete. On Premium and Enterprise plans work items can be archived and restored later.
  4. Add the automation rule above. It takes ten minutes and gives you an alert plus a copy of the main fields.
  5. Schedule backups if losing a day of work across the site would be serious.
  6. Decide whether you need an app. If your team deletes rarely and permissions are tight, the steps above may be enough. If many people can delete, or you have already lost work once, a restore app is cheap insurance.

What I'm building

I'm working on Undelete for Jira, a small Forge app that does one thing: keep deleted work items recoverable. It is not released yet. The plan for the first version:

  • tracking on for every project by default, with no per-project setup;
  • restore of fields, comments, worklogs, links and subtasks, one item or in bulk;
  • an alert when someone deletes many work items at once;
  • data stored on Atlassian's infrastructure.

Attachments are the hard part and will not be in the first version. If attachments are the thing you most need back, I would like to know, because it changes what I build first.

If you want early access, or just want to tell me what went wrong the last time someone deleted something: join the early access list.

FAQ

Can Atlassian Support restore a deleted Jira work item?
No. Atlassian's documentation states that its backups cannot restore individual deleted work items.

Does Jira Cloud have a recycle bin?
Only for whole projects, which stay in the trash for 60 days. There is no recycle bin for individual work items.

Will a restored work item keep its original key?
No. Any restore method creates a new work item with a new key.

Can I see who deleted a work item?
Yes, on paid plans, under Settings → System → Audit log, with the Administer Jira permission. Sites that are entirely on the Free plan have no audit log.

Can I recover deleted attachments?
Not through Jira and not through the restore apps listed above. Keep important files in a system that has its own version history.

I installed a restore app after the deletion. Will it find the work item?
No. These apps can only recover work items that were deleted after the app started tracking the project.

Sources

Top comments (0)