Deleted Record History guide
Jira Service Management deleted records: recovery and history
Use documented Jira Service Management recovery options and validate the result, with earlier exports available for historical reference.
On this page
Start with native recovery
Atlassian’s Jira Cloud recovery guide starts from a pre-deletion XML/CSV export or retained notifications. Its backup-based procedure restores a prior backup, exports the required work item and imports the selected CSV. Plan the restore destination and scope with the administrator before a site-level operation. See Restore deleted work items in Jira Cloud using local backup files.
Confirm identity and visibility
Record the native ID, customer, requester and last known dates before acting. Check whether filters, permissions, an archive or a merge explain the missing item. Ask an authorized administrator to confirm the record’s current state.
Check the recovered record
Reconstructed work may receive a new identifier. Keep the original key in the crosswalk, verify comment visibility and reconcile relationships. A readable earlier export is also useful for answering the historical question while recovery is arranged.
Use earlier captured history
An earlier export can show what was retained before the record changed. Keep its capture date and source identifiers visible, and restrict internal notes to the appropriate audience. For file evidence, open the saved file itself and retain its parent-record reference.
Plan the next capture through the Jira Service Management export guide. Related native documentation: Import data from a CSV file. The deleted-record history use case connects recovery preparation to longer-term archive access.
Plan ahead for useful record history
Preserve captured records before they change or disappear. Join the waitlist for invitation-only BackupPSA access.