How to make a Jira status report in Confluence that keeps every week
By Jake Marsh · Updated
To make a Jira status report in Confluence that keeps each week, add a Stillframe snapshot to the report page, give it the JQL for the work you report on, choose Chart and table grouped by status, and set Take a new snapshot to Every week. Every Monday (or the day you pick) Stillframe saves a dated copy of the result, and Compare shows what changed between any two weeks.
Why a live macro isn't enough for a status report
The Jira issues macro and Jira charts in Confluence show today's values every time the page opens. That suits a dashboard, but a status report is meant to say what was true on a given date. With a live macro, last month's report page shows this month's numbers, and nobody can tell what the team reported back then. A snapshot is copied onto the page once and stays that way.
Steps
- Create the report page in Confluence, with whatever headings and commentary your report uses.
- Type
/Stillframe snapshotwhere the numbers should go and insert the macro. Publish the page. - Click Set up snapshot. Enter the JQL, for example
project = WEB AND statusCategory != Done ORDER BY priority DESC, or pick a saved filter. - Pick the columns, such as Summary, Status, Assignee, Priority and Due date.
- Under Show, pick Chart and table. Set Group the chart by to Status and Chart type to Bar or Pie.
- Set Take a new snapshot to Every week, choose the day and an hour in UTC. Pick an hour shortly before the report is read.
- Click Preview to check the rows, then Save and take snapshot for the first version.
Reading the report later
| You want to know | Do this |
|---|---|
| What we reported on 3 November | History, then View on that version. A banner says you're looking at an older version |
| What changed since last week | History, then Compare on last week's version |
| Which items finished or dropped out | Compare lists Added, No longer in the result and changed fields with Before and After |
| The raw numbers for a spreadsheet | CSV on any version |
Work items are matched by id, so one that moved to another project shows its new key in the comparison instead of looking like a removal.
Keeping the schedule running
A schedule runs with the access of the person who last saved the settings. It pauses, with the reason shown to page editors, if that person can no longer edit the page, the macro is removed or the page is deleted. Another editor takes over by opening Settings and saving. A Confluence admin can also switch schedules off for the whole site in Confluence settings > Stillframe.
Monthly reports and one-off reports
Pick Every month and a day from 1 to 28 for a monthly report. For a report written by hand each time, leave it on Only when someone takes a snapshot and click Take snapshot now while writing it. Either way, every version is kept, up to 100 by default.
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. Every tier and the install link 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
Can I use currentUser() in a scheduled report?
Yes. It becomes the person who owns the snapshot, so assignee = currentUser() means that person's work items in every scheduled run.
Why was my JQL refused?
Functions that depend on who is searching, such as watchedIssues(), votedIssues() and issueHistory(), can't give the same answer in a background run. Write the condition with explicit values, for example watcher = "Ana Ruiz".
Does the report include work items the readers can't see in Jira?
It includes what the snapshot's owner can browse, and everyone who can view the page can read it. Treat it like a table pasted into the page, and set the page's permissions to match.
Can I put more than one snapshot on a report page?
Yes. Each macro is its own snapshot with its own JQL, schedule and history, and the page loads them from storage instead of asking Jira.
More Stillframe guides
- How to export Jira issues to a Confluence page as a static table
- How to save a Jira sprint report in Confluence at the end of each sprint
More Confluence guides
- How to baseline requirements in Jira (Tracestitch)
- How to find credit card numbers and Social Security numbers in Confluence and Jira (Spillproof)
- How to set a reminder on a Jira issue (Remindwell)
- How to find duplicate issues in Jira (Mergewell)