Jira Snapshots grabs Jira data and includes it in Confluence pages. The App exports the data from Jira and keeps a static copy of it, capturing the data at a specific time. As soon as users understand this core principle of the App, one of the first follow-up questions is: so where do you keep these Jira snapshots?

We are happy to announce that, as of today (May 2022), we store the Jira snapshots on Confluence. You no longer need to consider RadBee’s storage yet another place where your Jira data resides. We know that you trust Atlassian with your data, and that’s why we store it there.

This technical improvement, ticks many boxes:

1. Data residency for Jira snapshots data is always the same as of Confluence.

2. Your Jira snapshots are protected by the same Atlassian policies, practices, and legal arrangements which govern Jira data in its native location (on Jira).

3. Data protection, backup, archiving, and recovery for Jira snapshots are all covered by the same means you manage your Confluence data.

But wait, there are more advantages:

From now, it is easier to get your Security officer to approve the installation of the Jira Snapshots app. So, more options are available to you for exporting data from Jira.

The second advantage, and its huge, is that we no longer need to safeguard your Jira data. The things that Atlassian takes care of: securing their storage, data recovery plans, data residency solutions, certifications, and all the rest, take a lot of effort. And these are things we no longer need to worry about in regards to your snapshots. We freed a lot of energy to work, well- on enriching the App and boosting your productivity.

And: the previous implementation had a size limit of 1MB total volume for each snapshot. The change of storage releases this limit. The limit is now the size limit on attachments in your Confluence instance (by default, this stands on a whooping 100MB).

So, where exactly on Confluence are Jira snapshots stored?

Jira snapshot captures each snapshot as an attachment to the Confluence page.

You can check this out yourself. Add a Jira Snapshots macro to the page, publish the page and take the first snapshot. The following things happened under the hood:

1. The page has two new attachments. These attachments capture the new data that the app exported from Jira. Going forward, each new snapshot taken for the same macro will add a new version to the same attachments. This way- your Confluence attachments remain organized and are not cluttered by a sea of snapshots.

2. A new page version was created and added to the page history. This is not a new feature, but something Snapshots always had. When reviewing historical page versions, you see the historical snapshots.