Skip to main content

FAQ

Does the app capture issues that were deleted before it was installed?

Yes — with Basic tracking profile.

In Basic mode, the snapshot is built from the Jira deletion event itself. The app captures the deletion at the moment it happens — regardless of when the issue was originally created. So if an issue existed for two years before the app was installed, it will still be captured when deleted.

Extended tracking profile is different. Extended snapshots are built incrementally on each issue create and update event. If an issue has not been created or updated since the app was installed, there is no Extended snapshot for it yet. To cover those issues, run a Project Scan.

Will the restored issue get the same key as the original (e.g. PROJ-123)?

No. Jira does not allow reusing deleted issue keys. The restored issue will receive a new key (e.g. PROJ-456). The original key is preserved in the snapshot metadata and is visible in the detail view.

What happens if the project was deleted after the issue was deleted?

The restore operation will fail because the target project no longer exists. The failure is logged in the Audit Trail with a clear reason.

What happens if the issue type no longer exists in the project?

The restore will fail with a clear error indicating the issue type is unavailable. Check the Audit Trail for the specific reason — you may need to re-add the issue type to the project scheme before retrying.

Can regular users (non-admins) view and restore deleted issues?

The app uses two global permissions that are independent of Jira project roles:

  • Viewing, inspecting, and exporting snapshots: Requires the View deleted issue backups permission — granted to all users by default.
  • Restoring and permanently deleting: Requires the Manage deleted issue backups permission — granted to Jira Administrators by default, but can be extended to any user or group.
  • Restore also requires: Create Issue permission in the target project, since the issue is created in the context of the logged-in user.
  • App Settings and Audit Trail: Requires the Manage deleted issue backups permission.

A Jira Administrator can grant the Manage permission to non-admin users — for example, to a dedicated support or ops team. See Permissions for details.

How long are snapshots kept?

By default, 90 days for deleted issue records and 180 days for audit records. Both values are configurable in App Settings → Retention Policy.

Each record shows a countdown to its expiry date in the detail view — so you always know when you need to act.

Does the app track deletions in all projects automatically?

No. Tracking is off by default for all projects. An administrator must explicitly add projects to the Tracking list in App Settings. This is by design — it gives you control over which projects are protected and at what depth.

Can I restore only some fields — for example, comments but not worklogs?

Yes. The restore modal shows individual checkboxes for:

  • Comments
  • Worklogs
  • Issue links
  • Subtasks

You can enable or disable each option independently. Only the checked items are restored — the rest are skipped.

What is a Project Scan and when do I need it?

A Project Scan builds Extended snapshots for all existing active issues in a project. It is only relevant for projects using the Extended tracking profile.

You need it when:

  • You enable Extended profile on a project that already has issues created before the app was installed
  • You recently switched a project from Basic to Extended and want existing issues covered

The scan runs in the background — you can close the browser while it's running.

Learn how to run it →

Is there a limit on how many deleted issues I can see at once?

The list shows up to 99 records per search query. To find specific records beyond this limit, use the available filters (date range, issue type, keyword, deleted by) to narrow the results.

What does "partial" restore result mean?

A partial restore means the issue was created successfully, but some of the requested content could not be restored. For example:

  • The main issue was created, but 2 out of 5 comments failed to post
  • Worklogs were restored, but one worklog author is no longer active in Jira

The detail view shows exactly what was and wasn't restored. A partial result is logged in the Audit Trail with the specific failure reasons.

Can I undo a restore?

Not automatically. A restore creates a new Jira issue — you would need to delete that issue manually if you want to undo it.

What happens to the snapshot after a successful restore?

By default, the snapshot remains in the app's history after restore. This is intentional — it allows you to track the restore event, view who triggered it, and restore again if needed.

If you want the record removed after a successful restore, enable Remove record after restore in the restore options modal.

What's next?​