How to save a Jira sprint report in Confluence at the end of each sprint
By Jake Marsh · Updated
To save a Jira sprint report in Confluence, add a Stillframe snapshot to the sprint's review page with JQL such as sprint = "Team 4 Sprint 14", include the Status and Story point columns, and click Save and take snapshot on the last day of the sprint. The page keeps the sprint's work items and their status as they were that day. Take one on the first day as well, and Compare shows what was added, removed or changed during the sprint.
What this records, and what it doesn't
Jira's own sprint report lives in Jira and is read by people with Jira access. A snapshot is something different: a table and chart of the sprint's work items on a Confluence page, frozen on the day you took it, that anyone who can read the page can see. It doesn't draw a burndown chart. It does keep the record the review page refers to, even after unfinished items roll into the next sprint and their statuses move on.
Steps
- Create or open the sprint review page in Confluence.
- Type
/Stillframe snapshot, insert the macro and publish. - Click Set up snapshot and enter
sprint = "Team 4 Sprint 14"(the sprint's name or id). AddORDER BY statusto group the rows. - Pick the columns: Summary, Status, Assignee, your story points field and Sprint.
- Under Show, choose Chart and table, with Group the chart by set to Status.
- Click Save and take snapshot on day one to record the committed scope.
- On the last day, click Take snapshot now. That's the end-of-sprint version.
- Open History and click Compare on the day-one version to see scope added mid-sprint, items no longer in the sprint and status changes, each with before and after values.
- Click Lock once the review is done, so the page keeps that sprint's final version.
Reusing the page for the next sprint
Copy the review page for the next sprint. The copy shows "This page was copied"; click Set up a new one and change the sprint in the JQL. Choosing Copy snapshot here would bring the previous sprint's values instead, which is useful only if you want both on the page.
Example comparison
| Section | What it lists |
|---|---|
| Added | Work items pulled into the sprint after day one |
| No longer in the result | Items moved out of the sprint or to another board |
| Changed | Each item whose status, assignee or points changed, with the value on day one and on the last day |
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 schedule the end-of-sprint snapshot?
Schedules run daily, weekly or monthly at an hour in UTC, so a two-week sprint doesn't line up with any of them. Click Take snapshot now on the last day instead, or use Every day and pin the version from the last day.
Can I use openSprints() in the JQL?
Yes, but each new snapshot then follows whichever sprint is open at the time. For a review page about one sprint, name that sprint.
Can the team see the snapshot without Jira?
Yes. Anyone who can view the Confluence page can read it, which suits stakeholders who join the review but don't use Jira.
More Stillframe guides
- How to export Jira issues to a Confluence page as a static table
- How to make a Jira status report in Confluence that keeps every week
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)