BinSafe FAQ and troubleshooting

What BinSafe protects

What gets captured?

BinSafe keeps a snapshot of each work item while it still exists: summary, description, work type, status, priority, labels, components, versions, due date, reporter and assignee, custom-field values (up to 20 KB each), up to 100 comments, up to 100 worklogs, issue links, subtask references, and attachments up to 120 KB each (600 KB per work item). When the work item is deleted, the snapshot moves to the Recycle Bin.

What isn't captured?

Change history, watchers and votes; sprint, rank and epic-link fields; some Jira Service Management and plugin fields (request types, SLAs, approvals, customer organizations); comments and worklogs past the first 100; attachments over 120 KB or past 600 KB per work item (only their name and size are kept).

Are my existing work items protected right after install?

Not all at once. New and changed work items are captured right away. Existing work items are snapshotted gradually in the background after install, at about 2,300 a day, so a large site can take days to be fully covered. A Jira admin can speed this up with Recycle Bin → Settings → Snapshot a batch now. Settings shows the backfill's last run and any error.

What about work items deleted before BinSafe snapshotted them?

BinSafe keeps the basic details Jira sends when the item is deleted (summary, type, project, status and people) and marks the item Partial. Only those details can be restored.

Restoring

Does restore bring back the original key?

No. Jira Cloud never reuses a deleted work item's key or ID, so restore creates a new work item with a new key. The old key is kept on the restored item: in its first comment and in the issue property recycle-bin.original, so you can search for it.

What happens to attachments?

Files that were copied (up to 120 KB each, 600 KB per work item) are uploaded to the restored work item. Larger files were never stored; the Preview lists their names and sizes.

Why do some restores finish at once and others run in the background?

Small restores run straight away, and you see the new key when they finish. A restore that copies larger attachments goes to a background queue: any single stored file of 64 KB or more, or 300 KB or more of stored files in total. You'll see Queued and then the progress steps (comments, worklogs, links, attachments) until it's Done. You can leave the page; the restore keeps going.

How does BinSafe handle Jira rate limits?

When Jira answers "too many requests", BinSafe waits as long as Jira asks (up to 10 seconds per wait) and tries again. Large restores run in the background queue, so they don't depend on your browser staying open.

Can a double click create two copies?

No. Each deleted item can only be restored by one job at a time. A second click or a retry shows "already being restored", and an item that's already been restored shows its existing new key instead of creating another copy.

Permissions

Who can see and restore deleted work items?

• Jira admins: see everything, including the global Recycle Bin page, and can restore anything.
• Project admins, and users with Browse projects plus Delete issues: see that project's bin.
• Restoring also needs Create issues in the project.
• Work items that had an issue security level are visible only to Jira admins and project admins.

Data

Where is my data stored?

Only in Atlassian Forge storage, in the same data residency location as your Jira site, and it moves with your site. BinSafe has no external servers and makes no calls outside Atlassian. We can't see your data.

How long are deleted items kept?

A Jira admin chooses 30, 90 (default) or 365 days under Settings. A daily job permanently removes older snapshots of deleted items.

What happens to my data if I uninstall?

BinSafe can no longer read its data. Atlassian deletes it after its retention window (28 days at the time of writing). Reinstalling doesn't bring it back automatically.

Troubleshooting

A deleted work item isn't in the bin

• It may have been deleted before BinSafe snapshotted it. Check whether it shows as Partial; if it isn't there at all, it was deleted before install.
• You may not have access: you need Browse projects plus Delete issues, or project admin. Items with an issue security level are visible only to admins.
• The project may have been moved to trash: its items show as deleted; a restored project brings them back to live.
• To protect existing items sooner, a Jira admin can run Settings → Snapshot a batch now.

A restore is stuck on "Queued" or "Needs another try"

Large restores run in the background, so give it a few minutes and refresh. If it still shows Queued or Needs another try, click Restore again: a retry picks up the stalled job and won't create a duplicate. If it keeps failing, email support@yuvgev.com with the work-item key.

"This restore copies a large attachment…" error

The background queue didn't accept the job, so nothing was started. Wait a moment and try again.

Restore fails with a permission message

• "You can view deleted work items, but restoring them requires the Create issues permission": ask a Jira admin for Create issues in that project.
• "Only a Jira admin or a project admin can open it": the item had an issue security level.
• PARENT_FIRST: restore the parent work item first.
• PROJECT_GONE: the project was permanently deleted, so Jira can't recreate the item.

I see two restored copies

BinSafe doesn't start a second restore for the same item, and it shows the existing new key if you restore again. If you still see two copies, search the comments for the old key, check both items' recycle-bin.original property, and email support@yuvgev.com with both keys.

"An active BinSafe subscription is required to restore work items"

The site's BinSafe license is inactive. BinSafe keeps capturing deletions and purging old snapshots, but restore and settings changes are blocked until the license is active again. Billing is handled by Atlassian: contact Atlassian support.

Some fields or files didn't come back

Check the restore result and the Preview's "What will not come back" list. Jira rejects fields that aren't on the create or edit screen; sprint, rank and epic link are never written back; files over 120 KB weren't stored.

Still stuck? Email support@yuvgev.com with your site URL, the project and work-item key, and a screenshot.