Jira Cloud has no trash for work items, so a wrong bulk delete, a cleanup script or an automation rule that ran on the wrong JQL is hard to reverse. On paid plans the audit log shows who deleted what and when, but it cannot give the items back. Restoring many of them at once, with their parents, subtasks and links intact, is the part that takes the time.
Claervo Undo 3.x is built around that case. It runs on Atlassian (Forge), so nothing leaves your site.
What is new
Bulk restore: filter deleted work items by person, project, type or date, preview what will come back, and restore them in one run. Parents are created first, subtasks follow their story, and links between restored items point at the new keys.
Richer restore: parent and epic children, watchers, sprint (where Jira allows it), the original status through the workflow, and a trace comment plus a restored-from-<key> label so anyone can see where an item came from.
Service management aware: internal notes stay internal and public replies stay public after a restore; the trace comment is internal.
Project page: project administrators can restore work items of their own project without site-admin access. Every call re-checks the permission for that project.
Older work items: a slow hourly backfill mirrors work items that existed before you installed the app, newest first. It pauses when storage passes 60% or Jira rate-limits.
Privacy scope: exclude projects or work item types from protection and purge what was already mirrored.
Health tab and alerts: storage, backfill progress, Jira call usage, recent errors, and an alert when one person deletes an unusual number of items in a short window.
Limits, honestly
- Restored items get a new key; Jira does not allow reusing a deleted key.
- Comments and worklogs are re-posted by the app with the original author and date in the text.
- Attachment files, change history and votes do not come back.
- Protection starts at install; backfilled items may have a partial comment history.
- Jira delivers events with a delay. I saw up to about 10 minutes on a test site, so a deletion may take a few minutes to appear in the list.
If you try it and something in a restore surprises you, tell me. The restore preview and the "will not come back" list exist so that surprises happen before the click, not after.
Disclosure: I build Claervo Undo for Jira. Marketplace listing:
https://marketplace.atlassian.com/apps/1279190949
Question for you: when a bulk delete or an automation misfire hits your site, what part of the cleanup takes the longest - finding what was affected, or putting it back?
