Limitations
What the app cannot do, and why. Read this before you rely on it.
Most of these limits come from the Jira Cloud platform and apply to every app of this kind. We list them so that you are not surprised after a deletion.
A restored issue gets a new key
Jira Cloud does not allow an app to create an issue with a chosen key, so a restore always produces a new one, for example OPS-1184 comes back as OPS-1201. The Trash tab shows "Restored as OPS-1201" on the original row, and the new issue gets a comment naming the original key, who deleted it and when.
Update saved filters, links in other tools and bookmarks that pointed at the old key.
Events can arrive up to about 3 minutes late
The mirror is fed by Jira events. Atlassian documents a delay of up to about 3 minutes; on our test site we measured 1 to 4 seconds. An issue that is created and deleted inside that window may never reach the mirror, and the same goes for the last edit before a deletion, or for an issue deleted while the initial load has not reached it yet.
If a deleted issue is missing from the Trash tab, that is the most likely reason.
Attachment files are not restored
The mirror keeps attachment metadata only: file name, size, type, author and date. The files themselves are deleted together with the issue and cannot be recovered by the app. Use Atlassian's site backups for files.
Issue history is not restored
The changelog of an issue is not mirrored. A restored issue starts a new history that begins with the restore.
Storage: 1 GiB per production installation
Copies live in the Forge SQL storage that belongs to your installation. Atlassian limits it to 1 GiB per production installation. The Overview tab shows "Storage used" as an approximate figure and warns when usage passes half of the limit.
Keep the retention period short enough for your volume: 30, 90, 180 or 365 days, 90 by default. On our test site a thousand issues with three comments each took roughly 5 to 8 MiB.
Nothing is saved while the subscription is inactive
Without an active subscription the app does not run at all: no mirroring, no cleanup, no restore. Issues created or changed in that period are not in the mirror. After a renewal run the initial load again so the mirror catches up; the Trash tab reminds you about it.
Only Jira administrators can restore
The app lives under Jira settings → Apps and is available to Jira site administrators. Every operation checks the caller's administrator permission before the app acts. Delegating restores to project administrators is not available.
Comment and work log authors are noted, not set
The Jira API does not allow an app to set the author or date of a comment. Each restored comment starts with a line "Originally posted by
Links to deleted issues are skipped
An issue link is restored only if the other issue still exists or has already been restored. Otherwise the link is skipped and named in the restore result. Restore the other issue first, then the link can be recreated by hand.
Sub-tasks need their parent first
A sub-task is restored under its parent, so the parent must exist or be restored first. Restoring a deleted parent restores its sub-tasks after it and attaches them to the new parent key. A parent that was never mirrored, for example one deleted before the app was installed, cannot be restored, and neither can its sub-tasks.
Fields missing from the create screen are skipped
The restore copies the fields that exist on the project's create screen. A field that has been removed since, or a value that no longer exists, such as a deleted component, is skipped and listed in the restore result as not restored.
Jira Data Center is not supported
Issue Recycle Bin is a Forge app for Jira Cloud only.
Last updated 2026-09-17 · Questions: support@keelbits.com