Stillframe documentation (source for the public SFDOCS knowledge base)

Getting started

1. Install Stillframe from the Atlassian Marketplace. It installs in Confluence.
2. Connect it to Jira on the same site: Atlassian Administration > Apps > Stillframe > connect to Jira. One subscription covers both.
3. Edit a Confluence page, type /Jira snapshot and insert Jira snapshot (Stillframe). Publish the page.
4. Click Set up snapshot. Enter JQL or pick a saved filter, choose the columns in the order you want, and click Preview (it runs as you, so you see what you can see).
5. Click Save and take snapshot. A few seconds later the table appears with "As of" and the date and time.

What "frozen" means

• When a snapshot is taken, Stillframe copies the values of the chosen fields for every work item the query returns, as text. People appear by display name.
• The page shows those copies. It does not ask Jira again when someone opens the page, so the values do not change when the work items do, and readers do not need Jira access.
• "As of" shows the reader's local time and UTC, who took the snapshot, how many work items it holds, and the version number.
• Work item keys link to Jira (you can turn that off). Opening a link needs Jira access as usual.

Columns, sorting, charts, row limits

• Any field Jira lets you search can be a column, including custom fields, sprints, versions, labels, components, parent and linked items. The key is always the first column.
• Sort by any column, ascending or descending, or keep the JQL order. Readers can re-sort the table and page through it; this does not change the snapshot.
• Show a table, a chart, or both. Charts (pie or bar) group by one column; multi-value fields such as labels count once per value.
• The row limit is set per snapshot, up to the admin's cap (2,000 by default, 5,000 at most). When more work items match, the header says "row limit reached".

Versions

• Every snapshot is kept as a version. History lists them with date, size and who took them.
• View opens an older version on the page (a banner says so, with "Show the latest").
• Compare shows work items added, no longer in the result, and changed fields with before and after values. Work items are matched by id, so a moved work item shows its new key.
• Pin keeps a version forever (with an optional note such as "Signed off by the change board"). Unpinned versions beyond the admin's limit (100 by default) are removed oldest first.
• CSV downloads any version with an "as of" line on top.

Locking

Lock pins the current version and stops new snapshots, including scheduled ones, so the page keeps that record. Only the person who locked it, or a Confluence admin (Confluence settings > Stillframe > Snapshots), can unlock it. Settings cannot be changed while locked.

Schedules

• Daily, weekly (pick the day) or monthly (day 1 to 28), at an hour in UTC.
• A schedule runs with the access of the person who last saved the settings (the owner): only work items they can browse, and only while they can still edit the page.
• Schedules pause, with the reason shown to page editors, when the owner can no longer edit the page, the macro is removed from the published page, or the page is deleted. Another editor takes over by saving the settings.
• Admins can switch schedules off for the whole site.

JQL that cannot be snapshotted

Snapshots are taken in the background, so JQL must mean the same thing whoever runs it. currentUser() is replaced with the person taking the snapshot. These are refused: watchedIssues(), votedIssues(), issueHistory(), currentLogin(), lastLogin(), myApproval(), myPending(). Write the same condition with explicit values, for example watcher = "Ana Ruiz".

Who sees what

A snapshot never contains work items the person who took it could not browse. Treat a snapshot like a table you paste into the page: everyone who can read the page can read it.

Admin settings (Confluence settings > Stillframe)

• Fields that may never be captured. Blocked fields are not requested from Jira, cannot be chosen, and drop out of existing snapshots at their next capture.
• Most rows per snapshot, Versions kept per snapshot, Allow scheduled snapshots.
• Readers can open older versions and Readers can see the JQL (off: page editors only).
• Snapshots tab: every snapshot with page, owner, schedule and status. Activity tab: who created, captured, locked, unlocked or deleted what, and when.

Copied pages and templates

When a page with a snapshot is copied (or created from a template that contains the macro), the new page shows "This page was copied". Editors can Copy snapshot here (keeps the original date; needs view access to the source page) or Set up a new one.

Jira panel

On a work item, Confluence snapshots lists the pages whose latest snapshot includes it (only pages you can open), with the snapshot date.

Export

PDF and Word exports of the page include the frozen table with its "as of" line (first 300 rows; use CSV for more).

Privacy

Stillframe runs on Atlassian's Forge platform. It stores the snapshots in your site's app storage and sends nothing anywhere else. See the privacy policy for the full list.