How to recover a deleted issue in Jira (and what to do before it happens)

Someone deleted a Jira issue that mattered — a customer bug, a piece of scope, an incident record — and you want it back. The uncomfortable truth first: Jira Cloud has no one-click undelete for a single issue. Here’s what you can actually do, and the thing to set up so this never costs you again.

What you can (and can’t) do right now

• Native undelete: none, practically. There’s no button in the Jira Cloud UI to restore a single deleted issue. Once it’s deleted, the issue is gone from the project.
• Project-level trash is a different thing. Jira Cloud does have a trash for whole projects — a deleted project can be restored by an admin within a time window — but that’s for recovering an entire project you deleted, not one issue inside a project you’re keeping. It doesn’t apply here.
• Atlassian support / backup restore. Atlassian has stated plainly that its backups can’t restore individual deleted work items — a support restore works at the site or project level, not surgically for one issue, and it requires a pre-deletion backup to exist in the first place. Don’t count on this path.
• The audit log tells you who, not what. Jira’s admin audit log records the deletion event — actor and timestamp — which is useful for working out whether it was an accident and who to talk to. It does not store the issue’s field content, so it can’t restore the data.

So after the fact, your realistic options are reconstructing the issue from email notifications sent to watchers (if anyone kept them), or from whatever record you happened to keep — there is no native path that gets a single issue back as it was.

The real fix: keep the history before it’s gone

The only reliable protection against deletion is an independent record of what each issue contained — captured before the deletion, not scrambled together after. That’s the paid tier of an audit-trail app like Trailkeeper: it continuously captures each issue’s last-known state and field-change history to its own store, separate from Jira — but only for issues it was already tracking, from the point you installed it onward.

Why that matters for deletions specifically:

• A deleted issue isn’t a total loss — if it was already being tracked. You get its last captured state and change trail, enough to rebuild the issue’s fields yourself. It’s read-only, so this is a manual rebuild from captured data, not a one-click restore.
• Accountability that’s actually readable. Who deleted it, and the change trail leading up to it — in one place, not scattered across a raw admin log.
• It’s protection you set up once, before the mistake. Coverage only starts from install, which is exactly why “set this up now” beats “what do I do after” — an audit trail installed today can’t help with an issue deleted last year.

The takeaway

If you’re reading this after a deletion: check the audit log for who deleted it, try an Atlassian restore fast if it’s recent and important, and reconstruct from any record you have.

If you’re reading this before: the lesson is that Jira won’t save you from a deletion, so keep an independent audit trail of issue history now — it turns “the issue is gone” into “we can rebuild it and we know what happened.”