ClaervoAdministrator guide
Restore deleted work items, undo a bulk edit or an automation run, and see who changed what, from one console inside Jira administration.
1. Install and open
Install the app from Atlassian Marketplace for a Jira Cloud site. A Jira administrator opens Claervo Undo from Jira administration → Apps. Protection starts the moment the app is installed; there is nothing to configure.
2. What is protected
Every work item created or changed after installation is mirrored: fields, comments, worklogs, links and attachment names. The ledger records one line per field change with the actor, the previous value and the new value. Jira delivers events within seconds, occasionally minutes. Overview shows the coverage since install, the number of deleted work items waiting and the mirror size.
3. Restore a deleted work item
Deleted lists every deleted work item with its type, status, who deleted it and when, and whether the mirror is FULL or PARTIAL. Select Restore to open the preview: the fields, subtasks, comments, worklogs and links that will come back, warnings, and the list of what cannot be restored. Confirm, and the app checks that the item is still gone, creates it again with a new key, adds the subtasks, re-posts comments and worklogs with the original author and date at the top, recreates links and moves the item to its original status. The result and every step are recorded in Restores.
4. Read the ledger
Ledger → Changes shows field changes, deletions, comments, worklogs and links with the actor named: a person, Automation for Jira or a Marketplace app. Filter by time range and work item key, and export CSV.
5. Undo a batch
Ledger → Batches groups changes made by the same actor within a ten-minute window, merging short gaps, so a bulk edit or an automation run appears as one batch. Select Undo this batch to see the operations, the items that will be skipped and a sample of what will be reverted. Confirm, and each field is re-read and put back only if it still holds the batch's value; description and custom fields come back from the snapshot taken before the change. Undone ledger lines are marked as such, and the result is recorded in Restores.
6. Restores
Restores is the audit trail: requester, source work item, new key, status and per-step details. A partial result lists exactly what was skipped and why, for example a link target that no longer exists or a field Jira rejected.
7. Settings
Choose the retention period (30, 90 or 180 days; 90 by default) and run the clean-up on demand. A daily job removes mirror snapshots, ledger lines, deleted work items and restore records older than the retention period. Uninstalling the app removes everything it stored.
Known limits
Restored work items get a new key; Jira does not allow reusing a deleted key. Created dates and change history are not restored. Comments and worklogs are re-posted by the app user with the original author and date in the body. Attachment content is deleted with the work item and cannot be recovered; file names are listed. Watchers and votes do not come back. Items deleted before installation are restored with the few fields Jira includes in its delete event. Jira permissions, required fields and workflow validators can reject a field or a transition; the app drops that field, reports it and continues.