Blog ·
Jira for scrum masters: the board, reports and routine
Jira for scrum masters is mostly about three jobs: keeping the board an honest picture of the sprint, reading the reports that tell the team how it is really working, and holding the rhythm of ceremonies and follow-ups that a busy team lets slip. Jira gives you the board and the reports out of the box. The rhythm is the part you have to build yourself, and it is where a few scheduled tickets do more than any amount of reminding. This guide covers each job, the filters worth saving, and a starter calendar of recurring scrum master tickets.
Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.
If you own the backlog and decide what gets built, Jira for product managers is the closer fit. If you answer for dates and budgets, read Jira for project managers. A scrum master shares the board with both and needs something different from it: a view of how the team works, rather than what it delivers.
What a scrum master needs from Jira #
A scrum master's questions are about the process. Each one has a home in Jira.
| Question | Where the answer lives |
|---|---|
| Is the sprint on track? | The active sprint board and the burndown chart |
| What is blocked, and for how long? | A saved filter on blocked or stale work items |
| Did we finish what we committed to? | The sprint report |
| Is our commitment realistic? | The velocity chart across recent sprints |
| Is work piling up in one column? | The cumulative flow diagram |
| Did the retro actions happen? | Action tickets, labelled and filtered |
| Is the next ceremony prepared? | Recurring prep tickets with a due date |
The last two rows are the ones most teams leave out of Jira, and they are the ones a scrum master is most often judged on. A retro that produces five actions and follows up on none of them teaches the team that retros do not matter.
Set up the board so it tells the truth #
A scrum board is only useful if its columns match what the team actually does. Three checks pay for themselves:
- One column per real state. If work waits for review, give review its own column. A card sitting in "In Progress" while it waits for someone else hides the bottleneck.
- A visible blocked state. Either a Blocked status or a flag. A flag marks the card on the board without changing its status. Pick one convention and keep it.
- Work in progress limits on the busy columns. A limit on "In Review" turns a silent queue into a red column the whole team can see in standup.
Our Jira kanban board guide covers WIP limits in more depth, and Jira workflow examples has workflows you can copy if your current one has drifted from how the team works.
The reports to read before each ceremony #
Jira's scrum boards ship with a set of reports under the Reports tab. Atlassian describes the sprint report this way:
The sprint report shows the list of work items in each sprint. It's useful for your Sprint Retrospective meetings, and also for mid-sprint progress checks.
A few details from the same documentation matter in practice: the sprint report is board-specific, so it only includes work items that match the board's saved filter, and estimates on subtasks are not included, only estimates on parent work items. If your team estimates subtasks, the report will look emptier than the sprint felt.
Which report to open, and when:
| Ceremony | Report | What to look for |
|---|---|---|
| Daily standup | Burndown chart | A flat line for more than two days |
| Sprint review | Sprint report | Work completed versus work moved out |
| Retrospective | Sprint report and cumulative flow | Scope added mid-sprint, a column that kept growing |
| Sprint planning | Velocity chart | The range of the last few sprints, not the best one |
Read velocity as a range. A team that finished 21, 34 and 26 points has a planning range, not a target of 34. Our Jira sprint planning guide walks through using that range in the meeting, and Jira capacity planning covers adjusting it for leave and holidays.
Filters a scrum master should save #
Save these and pin them to a dashboard. Replace TEAM with your project key.
| View | JQL |
|---|---|
| Blocked or flagged now | project = TEAM AND sprint in openSprints() AND (status = "Blocked" OR flagged is not EMPTY) |
| Untouched for two days | project = TEAM AND sprint in openSprints() AND statusCategory = "In Progress" AND updated <= -2d |
| Added after the sprint started | project = TEAM AND sprint in openSprints() AND created >= startOfWeek() |
| Open retro actions | project = TEAM AND labels = retro-action AND statusCategory != Done |
| Overdue team routine | project = TEAM AND labels = scrum-routine AND due < now() AND statusCategory != Done |
The third filter is approximate, since startOfWeek() only matches the sprint start if your sprints begin on a Monday. Adjust the date to your own sprint start. Our Jira dashboard examples shows how to lay these out so a glance answers the standup question before anyone speaks.
The scrum master's routine nobody puts on the board #
Ceremonies have calendar invites. The work around them does not, and that is the work that slips. A typical calendar:
| Routine | Cadence | What goes wrong without a ticket |
|---|---|---|
| Sprint planning prep | Every sprint, two days before planning | The top of the backlog is not ready and planning stalls |
| Retro prep | Every sprint | The retro repeats the same three complaints |
| Retro action follow-up | Every sprint, mid-sprint | Actions are agreed and forgotten |
| Board hygiene check | Weekly | Stale cards and dead columns pile up |
| Impediment review | Weekly | A blocker lives for a whole sprint |
| Team health check | Monthly or quarterly | Morale problems surface as resignations |
| Working agreement review | Quarterly | The agreement describes a team that no longer exists |
| Definition of done review | Quarterly | Quality slips one exception at a time |
Every row is a recurring ticket. A ticket gives the routine an owner, a due date and a place on the board the team already reads. It also leaves a record: after six months you can show which retros produced actions and which actions were done.
How to create recurring scrum tickets in Jira #
There are three ways to get these tickets onto the board.
| Clone by hand | Jira Automation scheduled rule | A scheduling app | |
|---|---|---|---|
| Who creates the ticket | You, every sprint | A rule | A schedule in the project |
| Setup | None | A rule per routine | A rule per routine, in a form |
| "Every second Wednesday" | Whoever remembers | Fixed rate or a cron expression | Chosen in the form |
| You are on leave | The ticket is not created | Created on time | Created on time |
| Cost | Your time | Counts toward your plan's automation usage | App licence |
Clone by hand #
Keep a template ticket per routine and clone it each sprint. Our Jira task template guide shows how. It works until the sprint you are out sick, which is exactly the sprint the follow-up mattered.
A Jira Automation scheduled rule #
Jira Automation's Scheduled trigger can create a work item on a timer. A two-week sprint lines up with a fixed rate of 14 days. Monthly and quarterly routines need a cron expression, covered in our Jira cron expression guide, and every run counts toward your plan's automation usage, explained in Jira Automation pricing.
A scheduling app #
Recurring Work Items for Jira is our app, and recurring tickets are its whole job. A scrum routine becomes a rule in the team's project:
- Turn the app on for the project and choose who may schedule.
- Set the working week and add public holidays. A rule can roll forward or back to a working day, or skip the occurrence, when its date lands on a day off.
- Create a rule per routine. The schedule options are every N days, chosen weekdays every N weeks, a day of the month, or a weekday position such as the first Monday or the last Friday of the month.
- Name each ticket with tokens, for example
Retro prep {{now.date}}, so this sprint's ticket is not confused with the last one. - Put the checklist in the description and set the assignee, labels and a due date relative to the run.
It uses no Jira Automation quota, and every run, whether it created, skipped or failed, is written to the rule's history with its reason. A rule is scoped to the project it lives in, so the team's schedules never create tickets anywhere else. It is free for up to 10 users.
A starter set of recurring scrum rules #
For a team on two-week sprints that start on a Monday:
- Sprint planning prep, every second Thursday. Description: check the top of the backlog has acceptance criteria and estimates, confirm who is away next sprint, pull the velocity range.
- Retro prep, every second Wednesday. Description: open the sprint report, note scope added mid-sprint, pick a retro format, list last retro's open actions.
- Retro action follow-up, every second Tuesday, landing mid-sprint. Description: run the open retro actions filter and chase each owner.
- Board hygiene, every Friday. Description: run the untouched filter, close or re-plan anything stale, check WIP limits still fit.
- Team health check, on the first Monday of the month.
- Working agreement and definition of done review, every three months on the 1st.
Label every one scrum-routine, and label each retro action retro-action when you create it in the retro. Our Jira retrospective template has an agenda and a ticket layout to start from, and Jira daily standup covers running standup straight from the board.
When the manual way is enough #
If you run one team, the ceremonies happen on fixed days, and retro actions live on a whiteboard that the team actually looks at, you may not need any of this. A recurring calendar invite and a good habit will carry it. Scheduled tickets earn their place when you serve two or more teams, when the routine has to survive your leave, or when you want evidence of which follow-ups happened. For a broader comparison of the options, see Jira recurring tasks.
Frequently asked questions #
Should a scrum master own the Jira board configuration? Usually the scrum master proposes and the team agrees. Columns and WIP limits are a working agreement, so changing them is a retro conversation.
Which Jira report is best for retrospectives? The sprint report, because it shows what was completed, what was not, and what was added after the sprint began. The cumulative flow diagram adds where work queued up.
How do I get a retro prep ticket every sprint? Clone one by hand, create a Jira Automation rule with the Scheduled trigger on a 14-day rate, or create a rule in Recurring Work Items for Jira that repeats every two weeks on the day before your retro.
How do I make sure retro actions get done? Create each action as a ticket in the retro, give it an owner and a retro-action label, and put a mid-sprint follow-up ticket on the board that runs the open actions filter.