How to export Jira issues to a Confluence page as a static table

By Jake Marsh · Updated

To export Jira issues to a Confluence page as a table that stays the same, insert the Stillframe snapshot macro, enter a JQL query or saved filter, pick the columns and click Save and take snapshot. The work items are copied onto the page as text, stamped "As of" with the date and time, and anyone who can view the page can read them without Jira access.

Live list or static copy

Confluence's Jira issues macro embeds a live search: each time the page opens it asks Jira again, and readers without Jira access don't see the rows. That's what you want for a working list. When you need the page to show a fixed set of work items, such as a scope agreed with a customer, the items in an audit sample or the backlog as it stood before a planning session, a copy is the better fit. Copying rows out of Jira by hand loses the date and goes stale without anyone noticing; a snapshot says when it was taken on the page itself.

Steps

  1. Open the Confluence page and click edit.
  2. Type /Stillframe snapshot and insert the macro, then publish.
  3. Click Set up snapshot.
  4. Enter the search. Paste JQL such as project = SUP AND created >= 2026-10-01 AND created < 2026-11-01, or type part of a saved filter's name in Start from a saved filter (optional).
  5. Choose the columns under Columns (in this order). Any field you can search in Jira works, including custom fields, sprints, fix versions, labels, components, parent and linked work items.
  6. Set Sort by and Direction, or keep JQL order. Raise Row limit if more than 500 work items match.
  7. Leave Show on Table, click Preview to check, then Save and take snapshot.

What gets copied

Jira valueOn the page
StatusThe status name in its Jira colour
Assignee, reporter, other people fieldsThe person's display name
DatesFixed values in UTC
Labels, components, versionsAll values in one cell
Rich text fieldsPlain text, up to 500 characters a cell
Work item keyA link to Jira, unless you turn off Link work item keys to Jira

Readers can re-sort the table and page through it 50 rows at a time without changing the snapshot.

Getting the rows out again

CSV opens the snapshot as CSV text with an "as of" line on top; copy it into a spreadsheet or a .csv file. Exporting the Confluence page to PDF or Word includes the table with its date, up to the first 300 rows.

When the copy should be refreshed

Click Take snapshot now to replace what the page shows with today's values. The old copy stays in History, so nothing is lost. To stop anyone replacing it, click Lock. From then on only the person who locked it, or a Confluence admin, can release it.

What it costs

Stillframe is $8 a month for up to 10 users, or $80 a year, and $1.30 per user a month from 11 users, billed by Atlassian with a 30-day free trial. The install link and every tier are on the Stillframe page.

Stillframe: Jira Snapshots in Confluence

Freeze a JQL result on a Confluence page with the date it was taken. Version history, compare, lock. Readers need no Jira access. From $8 a month for up to 10 users.


Questions

How many Jira issues can I export to one page?

Up to 2,000 per snapshot by default, and up to 5,000 if a Confluence admin raises the limit. When more match, the header says the row limit was reached.

Can I export Jira issues from another Atlassian site?

No. Stillframe reads the Jira site that shares the Confluence site it's installed on.

Does exporting change anything in Jira?

No. Stillframe only reads Jira; it has no permission to edit work items.

Will people who aren't in Jira see the table?

Yes, if they can view the page. Opening a work item link still needs Jira access.


More Stillframe guides


More Confluence guides