Issue Recovery for Jira

Jira Cloud has no recycle bin. A deleted issue takes its description, comments and field values with it. Issue Recovery keeps a copy of each issue as it changes, so a deletion can be undone.

Not yet listed on the Atlassian Marketplace. The listing is being prepared.

Read the documentation Email support

RCV-5Last comment on the restored issue

This issue was restored by Issue Recovery for Jira.

Original key: RCV-4
Original reporter: Dana Ortiz
Original creator: Dana Ortiz
Original created date: 2026-11-02T09:14:00.000-0700
Original status: In Progress

Deleted by Sam Lee on 2026-11-12T16:20:41.000Z
Restored by Priya Shah on 2026-11-13T15:02:07.000Z

Attachments not restored: wiring-diagram.pdf, screenshot.png
Not restored: Fix versions: 2.3 (removed)

The note Issue Recovery adds when it restores RCV-4 as RCV-5. Wording from the app; names, dates and files are examples.

What it does not do

Read this before you install.

It cannot recover an issue that was deleted before the app was installed.
An issue is only covered once the app has saved a copy of it. Issues that existed before install are covered after they next change, or after you run a backfill.
Attachment files are not saved or restored. Their names are listed in the note.
Links to other issues are shown in the saved copy and listed in the note. They are not re-created.
The restored issue gets a new key and starts in the first status of its workflow. The original key, status, history and watchers do not come back.
Worklogs and Jira Service Management request details are not covered.
It runs on Jira Cloud only.

How a restore goes

The deletion is logged
Key, summary, project, type, who deleted it and when. Filter by project, person and date, or search by key or words in the summary.
Can be restoredNot covered
You open the saved copy
The last saved copy: fields, description with its formatting, comments, links and attachment names.
Restore as a new issue
It comes back as a new issue
Same project and issue type, with summary, description, priority, labels, components, versions, due date, assignee and custom fields carried over. Comments come back in order, each headed by its original author and date.
Restored as RCV-5

The restored issue gets a note with the original key, reporter, created date and status, who deleted it, who restored it, and anything that could not be restored. Inside the app, the first screen shows how many of your issues are covered and how many are not.

Your data stays in Atlassian

Where the data lives: Saved copies are stored in Atlassian's Forge storage, inside Atlassian's cloud. The app has no servers of its own and makes no calls outside Atlassian. Atlassian reports it as eligible for the Runs on Atlassian program. See the privacy policy.
Retention and erasure: Records of deleted issues are kept for 90 days by default. A site admin can set that anywhere from 30 to 365 days, erase one person's name and account from every record, or erase everything the app holds.
Who can use it: Jira site admins see deleted issues from every project. Project admins see the projects they administer. Nobody else sees anything. The app checks those rights again each time someone opens or restores an entry.
Price: Free for Jira sites with up to 10 users. Larger sites pay per user through Atlassian, with a free trial. The price will be shown on the Marketplace listing. A site without a license can still see the log and the saved copies, but cannot restore.

Before you install

The documentation covers coverage, backfill, restore, retention and erasure in full.