Skip to main content

FAQ

Short answers to the questions Jira administrators ask most about Storage Saver. Each one links to the page that explains more.

Before you install​

Where do moved files go, and do they leave Atlassian?

Into Storage Saver's own storage, which Atlassian hosts for the app, where they no longer count toward your site's Jira storage. They never leave Atlassian: Storage Saver talks to no server outside Atlassian and needs no external account. A moved file stays with its work item, where people download or restore it from the Storage Saver panel or the project page. See Data & Security.

Do JQL, exports, backups, the REST API and automation rules see moved files?

No. A moved file is no longer a Jira attachment, so the REST API, JQL attachment search, exports, backups, automation rules and other apps that read attachments no longer see it. It stays reachable from its work item through Storage Saver, and a Jira administrator can list every moved file by exporting the recovery manifest. If a rule or an integration reads the files of recent work items, set a minimum age, so that Storage Saver moves no file younger than that.

Does Storage Saver use up our Jira Automation allowance?

Not for its own work. Storage Saver moves, restores and scans files itself, and none of that runs as a Jira Automation rule, so its own work uses none of your automation allowance.

Why can't Storage Saver move files larger than 500 MB?

500 MB is the largest file Storage Saver restores, so it moves nothing larger. A larger file stays in Jira, and the storage report counts such files under What these figures cover. A restore must also fit your site's maximum attachment size, which a Jira administrator sets in Jira's attachment settings; a larger moved file can still be downloaded. See Storage Report.

Why are images pasted into a comment never moved?

An image or file pasted into the description, a comment or another field is one of the work item's attachments, and the text shows it from there. Moving it would delete that attachment and leave an error in the text where the file was, so Storage Saver never moves a file that the work item's text uses, and the text stays as it was. It reads the whole work item, every field and every comment, when a move is asked for and again right before the Jira attachment is deleted. The pickers list such a file under Cannot be moved: "Used in the description or a comment. Remove it from the text to move it." See How a move works.

Who can see a moved file?

Everyone Jira shows the work item to: they see the file on the work item's Storage Saver panel, once someone has added the panel, and can download it. Restoring the file also takes Create attachments, and deleting the stored copy takes Delete all attachments, or Delete own attachments for a file you uploaded. Two places show file names to administrators beyond that: the project page, to the project's administrators and Jira administrators, and the recovery manifest, to Jira administrators. See Permissions.

What happens if we uninstall Storage Saver?

Moved files do not come back into Jira. Atlassian keeps the app's data for 28 days after an uninstall, and recovering the files within that time is a support request that Terano Apps must raise within 21 days of the uninstall. Before you uninstall, restore what you still need, one file at a time, and export the recovery manifest. See If you uninstall Storage Saver.

After a move​

I moved files, so why has the storage figure not dropped yet?
  • Check that the moves have finished. While a file's tile reads Queued, Moving or Removing from Jira, its Jira attachment is still there. Files move one at a time across the whole site.
  • Jira's own storage figure is not updated at the moment of the move; it catches up later.
  • The storage report on the Overview tab shows the files as the last scan found them, so files moved since then stay in its figures until a new scan, started with Scan again, has finished.

See Storage Report.

A file is gone from a work item's attachments. Where is it?

If Storage Saver moved it, it is listed on the work item's Storage Saver panel. The panel is not there until someone adds it: open the work item, select View app actions, then Storage Saver. Until then, a file moved from the project page or in a bulk move is simply gone from the attachments. A Jira administrator can show the panel on every work item of the project at once, see Work Item Panel. The project's administrators also find the file on the project page.

What does Restore do to links and attachment ids?

Restore puts the file back on its work item as a new attachment, with a new id, so links to the original attachment stop working. Storage Saver's record keeps the original author and date, and the file's tile keeps showing them. Storage Saver also keeps its stored copy until someone presses Delete on the tile; that deletes only the stored copy, and the Jira attachment stays as it is. See Project Page.

What happens to a stored copy when its work item is deleted?

It stays in Storage Saver's storage: deleting a work item does not delete the stored copies of its files. Nobody can download or restore them any more, because both need Jira to show the work item. The project's administrators and Jira administrators still see such files on the project page, and can press Delete there to remove a stored copy. Restore or download what you need before you delete a work item. See Permissions.

When a move does not finish​

A file's tile disappeared, and the file is still among the work item's attachments. What happened?

The move stopped at its last step. Right before the delete, Storage Saver checks the work item again. If it cannot confirm that the file is unused, or Jira refuses the delete for good, Storage Saver discards its copy, and the file stays in Jira as it was, with no entry in the app. Nothing needs cleaning up. To see whether the file can be moved now, open the panel's picker: if it cannot, the reason is beside it under Cannot be moved.

A move failed. Is the file lost?

No. A move that fails before its last step leaves the file in Jira. If the last step, the delete, keeps running into temporary errors until its attempts run out, Jira may have removed the original without confirming it, so the Saved files tab tells you to check the work item (the stored copy was verified first). Either way, look at the work item:

  • The file is still among its attachments: press Remove on its tile, on the panel or the project page. That clears the failed move, and the file can be moved again.
  • The file is gone from its attachments: open the work item's Storage Saver panel, adding it first if it is not there. The verified copy is now the only one, and the panel shows the file as moved.