Blog ·
Jira sprint review: the report, the demo, and the ticket that books it
A Jira sprint review is the meeting at the end of a sprint where the team shows stakeholders what was finished, using the board and the Sprint report as the record of what happened. In Jira Cloud you open it from the space's Reports tab, choose Sprint Report, and pick the sprint. The report lists completed work, work not completed and work added after the sprint started, with a burndown above it. This guide covers what that report counts (and what it quietly leaves out), an agenda that fits in an hour, and how to make sure the review itself is booked every sprint instead of depending on somebody remembering.
Statements about Jira here are as of October 2026, from Atlassian's own Cloud documentation and template pages. Atlassian now calls a project a space and an issue a work item. This guide uses both, because most people still search for the old words.
Sprint review vs retrospective #
The two meetings sit next to each other on the calendar and get confused constantly. They answer different questions and invite different people.
| Sprint review | Sprint retrospective | |
|---|---|---|
| Question | What did we build, and what should we build next? | How did we work, and what do we change? |
| Audience | Team plus stakeholders, product owner, sometimes customers | The team only |
| Main input | The increment, the board, the sprint report | The team's experience of the sprint |
| Output | Feedback and backlog changes | A short list of process actions |
| Jira artefact | Sprint report, backlog edits | Action items, a linked Confluence page |
Atlassian's sprint review template page puts the purpose plainly:
"An agile sprint review template is your roadmap for showcasing what your team has accomplished during a sprint."
If you were looking for the inward-facing meeting, the Jira retrospective template guide covers it. The rest of this page is about the review.
Open the sprint report #
The sprint report is the one screen most reviews are built around. Atlassian's documentation (as of October 2026) gives the path:
"Select the Reports tab from your space navigation, then Sprint Report. Select the relevant sprint from the sprint dropdown."
Two conditions apply before it shows anything useful:
- It only exists on Scrum boards. A Kanban board has no sprints and so no sprint report. Kanban teams use the cumulative flow diagram or a filter of work resolved in the period instead.
- The page documents company-managed spaces. Team-managed spaces have their own reports, and the details differ.
What the report counts #
The documentation is specific about how the numbers are made, and each rule changes what you should say in the room:
- "The sprint report is board-specific": it only includes work items that match the board's saved filter. Work that the team did but that lives outside the filter does not appear.
- "Work items added after the sprint starts are indicated with an asterisk." That asterisk is the scope-change story. Say it out loud rather than letting a stakeholder find it.
- Done means the right-most column. A work item counts as done when it sits in a status mapped to the board's last column. If "Ready for release" lives in a middle column, finished work reads as unfinished.
- "Estimates on subtasks are not included in the sprint report": only estimates on parent work items count.
- A story point value shown as 3 → 3.5 means the estimate changed during the sprint.
The trap most teams fall into is reading the sprint report as a velocity scorecard in front of stakeholders. It is a list of work. The review is about the increment, and the numbers are context for it.
The burndown above the list #
The grey line is the guideline, from the starting total to zero, flat over non-working days. The red line is the remaining estimate as it actually moved, and it rises when work is added. A red line that climbs in week one and then drops steeply in the last two days is worth one sentence in the review, because it usually explains why something slipped.
A sprint review agenda that fits in an hour #
Atlassian's template page suggests four steps: define goals, summarize completed work, add metrics and progress, facilitate feedback. In practice that becomes:
- Sprint goal, two minutes. Read it out. Say whether it was met.
- Demo, thirty minutes. Show working software, not tickets. One person per item, in the order a user would meet the features.
- What did not get done, five minutes. Open the sprint report's not completed list and say what happens to each item: next sprint, back to the backlog, or dropped.
- Numbers, five minutes. The burndown and the scope added after the start. Keep it short.
- Feedback and backlog, fifteen minutes. Stakeholders react; the product owner edits the backlog live, in Jira, while people are still in the room.
- Next sprint preview, three minutes. What is likely to be pulled in, so stakeholders know when to come back.
Write new backlog items during step 5, not after. Feedback written down later is feedback half lost.
Where the review lives in Jira #
A review has three pieces, and it helps to decide where each one belongs:
- The record of the sprint. The sprint report and the board. Nothing to set up.
- The notes and feedback. A Confluence page linked from the sprint, or new backlog items with a
sprint-reviewlabel so you can find them with JQL later. - The meeting itself. A calendar invite, and ideally a work item on the board: assigned to the person who prepares the demo, due on the last day of the sprint, with the agenda as its description or as subtasks.
That third piece is the one that goes missing. A review with no owner tends to start with ten minutes of "who is showing what", and a review that was never booked leaves no trace at all.
Make the review appear every sprint #
There are four common ways to get a "Sprint review" work item onto the board each sprint.
| Clone last sprint's | Jira Automation scheduled rule | Template app plus a rule | Recurring rule | |
|---|---|---|---|---|
| Needs a person each sprint | Yes | No | No | No |
| Prep subtasks included | Copied | One action per subtask | Yes | Yes, ordered |
| Date in the title | Typed by hand | Smart values | Variables | Tokens |
| Where the schedule lives | Somebody's head | The rule | Jira Automation | The same rule |
| Record of each run | None | Audit log | Audit log | Run history per rule |
Cloning is free and works until the person who does it is away. A Jira Automation scheduled rule is the native option: it runs at a fixed rate or on a cron expression, and the syntax and its traps are in Jira cron expression. Automation runs are metered against your plan's monthly allowance, which is explained in Jira Automation pricing; a fortnightly create rule spends very little of it. A template app such as Issue Templates for Jira stores the work item and its subtasks, and takes its clock from an Automation rule.
A recurring rule in Recurring Work Items for Jira keeps the template and the schedule in one record. Pick a pattern such as every second Friday, read the preview of the next runs before saving, and add the prep steps as subtasks:
- confirm the demo order with the team;
- check the board's done column matches what is really finished;
- invite stakeholders and post the link to the sprint report;
- create the feedback page.
The summary takes date tokens, so each sprint gets "Sprint review: 30 October 2026" rather than a column of identical titles; the vocabulary is on the tokens page. The project's working days and holidays decide what happens when the date lands on a day off. Every run is written to the rule's run history, created, skipped or failed, with the reason. The app is free for up to 10 users.
When the manual way is enough #
You do not need a scheduled work item if:
- The review is already a recurring calendar event that everyone attends, and the same person always prepares it.
- Your sprints change length often. A schedule built for a fixed cadence will drift from sprints that do not have one. Book the review when you start the sprint instead.
- You run one team on one board. Starting the sprint is already the moment to create the review item, and cloning takes seconds.
A recurring rule earns its place when several teams run reviews, when the person preparing it rotates, or when someone has to show later that reviews actually happened.
Frequently asked questions #
Is there a sprint review report in Jira? Yes. The Sprint report, under the space's Reports tab on a Scrum board, is the closest built-in thing. Atlassian's documentation describes it as useful for retrospectives and mid-sprint checks, and it serves the review just as well.
Does Jira have a sprint review template? Atlassian publishes a sprint review template page that bundles a Scrum board, backlog, sprint progress and issue tracking. It sets up a space; it does not create a review work item each sprint.
Who should attend a sprint review? The team, the product owner and the people who care about the increment: stakeholders, sometimes customers. Keep the retrospective for the team alone.
Why is finished work showing as not completed? Usually because its status is not mapped to the board's right-most column, or the work item does not match the board's filter. Fix the column mapping and the report follows.
For the meeting before this one, see Jira sprint planning, and for the scrum master's whole routine, Jira for scrum masters.