Undelete for Jira — user guide
Last updated: 22 October 2026
What it does
Jira Cloud has no recycle bin for single work items: once deleted, a work item is gone. Undelete keeps a copy of your work items inside your own Atlassian site, and when one is deleted it lands in a bin. From there a Jira administrator brings it back with one click, alone or in bulk.
Requirements
- Jira Cloud.
- You must be a Jira administrator to open the bin. The app acts with your permissions.
- Nothing else: no account, no token, no configuration. Protection starts as soon as the app is installed.
Where to find it
Jira → Settings → Apps → Undelete.
What comes back
- Summary, description, type, space, priority, labels, components, versions, due date, assignee, reporter, parent and environment, plus custom field values that Jira accepts on creation.
- Comments, in order, each starting with “Originally posted by @author on date”.
- A note at the end of the description with the original key, the deletion date, the names of attachments that could not be restored, and any field Jira did not accept.
What does not come back, and why
- The same key. Jira does not allow a key to be reused, so the restored work item gets a new one; its description links back to the original.
- Attachment files. Their names are listed in the restored work item.
- Work items deleted before the app was installed. There was nothing to copy yet.
- Full content of items never changed since installation. They are copied on their first change. If one is deleted before that, the bin shows “Basic fields only” and restores the basic fields Jira provides.
- Fields Jira refuses (a deleted component, an archived version, a deactivated user, a field not on the create screen). The app removes them, tries again, and lists them in the note: nothing is dropped silently.
Sub-tasks
Deleting a work item also deletes its sub-tasks, and Jira does not report those deletions to apps. Undelete keeps track of sub-tasks anyway: they appear in the bin marked “deleted together with” their parent. Restore both together and the sub-task is created under the new parent. A sub-task whose parent is still in the bin asks you to restore the parent first.
How long items stay in the bin
90 days by default. Change it at the bottom of the page (7 to 365 days). A daily job removes older entries. You can also remove entries yourself at any time.
Licence
Copying and viewing the bin never stop, even if the subscription lapses, so nothing is lost on the day someone deletes something. Restoring needs an active subscription or trial. Removing entries is always free.
Contact
- Support portal: pieranlab.atlassian.net/servicedesk/customer/portal/1
- E-mail: support@pieranlab.cloud
- Service levels: support policy (first answer within 2 working days).
See also
The privacy policy and the security statement.