Bitwerf · Overview

Deleted Issue Recovery for Jira by Bitwerf – Documentation

Jira Cloud has no recycle bin: a deleted issue is gone, together with its comments and attachments. This app keeps a copy of every issue, records every deletion with who did it, and restores a deleted issue in one click.

Coming to the Atlassian Marketplace. Want it on your Jira site first? Email hello@bizzkitt.ai and we let you know the day it is live.

List of deleted issues with who deleted them, when, and whether the full content was kept

Where to find it

Jira settings → Apps → Deleted issue recovery. Only Jira administrators can open it.

How it works

Install. The app scans the issues you already have, in batches, and keeps a copy (a snapshot) of each one. On a site with tens of thousands of issues this takes a few hours; the status card shows the progress.
Every 5 minutes the app looks for issues that were created or changed since its last check and refreshes their snapshots.
When an issue is deleted, Jira tells the app which issue it was and who deleted it. The app records the deletion and keeps the snapshot for your retention period.
Restore from the list whenever you need to.

What a snapshot contains

Summary, description, environment, issue type, status, priority, resolution, assignee, reporter, creator, labels, components, fix and affected versions, due date, parent, subtask keys, issue links, time tracking, custom fields with a value, up to 200 comments, up to 100 work log entries, and the names and sizes of attachments. A snapshot is at most 200 KB; for very large issues the app drops, in this order, custom fields, work logs, the attachment list, the oldest comments and finally the description formatting, and tells you what it left out.

Full or basic

Badge	Meaning
Full	The app had a snapshot of the issue. You can read everything and restore it. Changes made in the 5 minutes before the deletion may be missing.
Basic only	The issue was deleted before the app had seen it (for example during the first scan, or in a project outside your scope). Only what Jira reports with the deletion is known: key, summary, type, project, status, reporter, creator, created date, who deleted it and when. It can't be restored.

Detail of a deleted issue with description, comments, work log and attachment names

Restoring an issue

Open the record and click Restore. The app creates a new issue in the same project with the same type and the content of the snapshot. Jira does not allow reusing the old key, so the restored issue gets a new key; the record shows the link.

Comments are re-posted. Each starts with a mention of the original author and the original date, followed by the original text.
Work log entries are re-added with their original start date and time spent.
Issue links are recreated when the other issue still exists.
Status: the issue is moved back to the status it had, when the workflow allows that transition from the first status.
A recovery note is added as a comment: original key, who deleted it and when, when the content was captured, and anything that couldn't be restored.
Fields Jira refuses (for example a custom field that is no longer on the screen, or a reporter you can't set) are skipped and listed in the result; the rest is restored.
Attachments can't be restored: Jira deletes the files with the issue. Their names and sizes are listed so you can ask the author for them.
Sprint, rank, epic link and Jira Service Management request fields are not restored; set them again by hand.

You can untick comments, work logs, status or the note before restoring.

A restored issue with its comments and work log

Audit trail and export

The list shows every recorded deletion with the key, summary, project, type, who deleted it and when, and whether the full content was kept. Search by key or summary, filter by project, by the person who deleted, or by restored status, and download everything as CSV.

Settings for Jira administrators

Keep records for 30 days, 90 days, 180 days, 1 year (default) or 2 years. After that the record and the snapshot are removed.
Projects: protect all projects, or only the ones you pick. Changing the scope starts a new scan.
Check for changes now runs the 5-minute check immediately.
Delete a record removes one deletion record and its snapshot. Delete all records removes all of them.

Settings: retention, protected projects and maintenance

Data and privacy

Snapshots and deletion records live in the app's Forge storage on Atlassian's infrastructure, in the same region as your Jira site. They contain issue content and the Atlassian account IDs of the people involved; names and avatars are shown by asking Jira when you open the app. Deletion records are kept for your retention period; snapshots of issues that still exist are kept while the app is installed, and Atlassian removes all stored data after the app is uninstalled. Every week the app reports the account IDs it stores to Atlassian's personal data reporting and removes closed accounts from its records. Bitwerf runs no servers for this app, uses no analytics and cannot see your data. See the privacy policy.

Limits

Snapshots are refreshed every 5 minutes; the last few minutes before a deletion can be missing.
200 KB, 200 comments and 100 work log entries per issue.
Attachments are not kept.
Issues deleted before the first scan reached them get a basic record only.

Pricing

Free trial for 30 days, then priced per user through your Atlassian bill. Teams of up to 10 users pay $0.01 per month.

Support

Email hello@bizzkitt.ai. We answer within 2 business days (Central European Time).

Bitwerf is a trade name of BizzKitt B.V., Frederikstraat 67, 3034 LD Rotterdam, the Netherlands (KvK 42149345, VAT NL869932354B01). Support · Privacy · Terms