Reference material for Snapshots — definitions, supported field types, the JQL primer, and a glossary. Use this section when you need a quick fact, not a tutorial.
Jira query language
-
Jira JQL Cheat Sheet — common JQL patterns used to drive snapshots, including subtleties specific to Snapshots' multi-level
$keyreferences.
Glossary
-
Snapshot — a static capture of Jira data at a specific moment, embedded in a Confluence page.
-
Level — a layer of data in a snapshot. Level 1 runs first; subsequent levels run for each level-1 result, referencing it via
$key. -
Sticker — a label attached to a specific snapshot version, used to find significant snapshots later.
-
Compare — the on-page action that shows the difference between two snapshots of the same page.
-
Access Agent — the companion app on Jira that grants Snapshots read access to Jira data.
-
JSON attachment — the file on each Confluence page where a snapshot's actual Jira data is stored.
-
Take snapshot — the action that captures current Jira data into the snapshot, generating a new page version.
Limits and constraints
-
Per-snapshot work item count: practical limit governed by Confluence attachment size (typically 100 MB) and Jira API rate limits. There are users with snapshots containing more than 50K work items.
-
Maximum levels per snapshot: no fixed cap; practical cap is the Confluence page width. Some users have snapshots with 7 levels.
REST endpoints
-
Per-macro automation endpoint — see Triggering snapshots automatically.
-
Site-level global automation endpoint — see Administering Snapshots automation.
-
Backup automation endpoint — see Backing up and restoring snapshots.
Atlassian Marketplace listing
The current price tier and trial terms are on the Marketplace listing: Snapshots of Jira data into Confluence.
What's next
-
Snapshots Cloud — Start here — the manual home if you've reached this page by accident.
-
Trust, data and security — the substantive answer to most "is this safe to use" questions.