Documentation
For the person installing and configuring the app. If you just want to read the numbers, the user guide is the one you want.
What you need
- Jira Software — the app reads boards and sprints through Jira's Agile API, which exists only for Software projects. A Business or Work Management project has no boards.
- A Scrum board with sprints. Kanban boards have no sprints, so there is no window to measure capacity against. The app will say so rather than showing zeros.
- Project admin permission to change anything. Anyone who can browse the project can read the dashboards.
Installing
Install from the Atlassian Marketplace. A site admin approves the permissions once, and the app appears in two places:
| Where | What you get |
|---|---|
| Apps → Sprint Verdict | The full app, six pages in the sidebar |
| Project → Capacity | The same pages as tabs, scoped to that project's boards |
Nothing else is required. There is no account to create, no key to paste and no service to connect — the app has no backend of its own.
Permissions, and why each one
Ten scopes, and it is worth knowing that they come from two different systems. Jira's platform API wants classic scopes; the Agile API accepts only granular ones and also requires granular platform scopes that classic does not satisfy. That is why the list looks inconsistent — it is not.
| Scope | What it is for |
|---|---|
read:jira-work | Issues, fields, boards, sprints, project metadata |
write:jira-work | The one write: your team configuration |
manage:jira-project | Required by Jira to write that project property |
read:jira-user | Assignable users, for the "add someone" picker |
read:project:jira | Required by the Agile board list |
read:issue-details:jira | Required by the Agile backlog and sprint-issue endpoints |
read:jql:jira | Required by the Agile sprint-issue endpoint |
read:board-scope:jira-software | Boards and backlogs |
read:sprint:jira-software | Sprints and their issues |
storage:app | Board display preferences, on Atlassian's own storage |
No permission lets the app act beyond what you can already do. Scopes never override Jira's own permissions. On top of that the app checks each viewer explicitly: reads are filtered to projects you can browse, and every write requires project admin on that project, both verified against Jira on each request.
There is no egress permission. The app makes no outbound network requests at all.
First-time setup
Three steps, about five minutes. Do them in this order — the estimation field affects everything downstream.
1. Estimation field
Settings → Estimation field.
The app auto-detects Story Points. If your numbers look wrong, or everything reads zero, this is almost always why.
Pick whatever your team actually estimates in:
| You estimate in | What to do |
|---|---|
| Story points | Nothing — auto-detected |
| A custom numeric field (dev days, complexity) | Pick it from the dropdown |
| T-shirt sizes on a select list | Pick it, then give each option a number |
| Original time estimate | Pick the time-tracking field; seconds convert to hours |
| Nothing at all | Switch the metric to Issue count |
Settings are saved per board and shared with everyone who opens that board.
2. Team
Team → Who's on the team.
Everyone with work in the current sprint appears automatically, marked from issues. Add anyone missing.
Then uncheck anyone who should not count towards capacity — managers, contractors, people who occasionally pick up a ticket. Their work still shows on the sprint page; it simply stops making the team look overloaded. Set allocation for part-timers: someone at 60% has 60% of the days.
3. Leave
Team → Where leave comes from. Three options:
- Jira issues (recommended). Choose your leave project from the dropdown. The app reads it and stores nothing. Leave keeps Jira's history, approvals and audit trail.
- Manual only. Type leave in by hand; it is stored in your Jira as a project property.
- Both. Read from Jira, and keep hand-typed entries too.
Press Test it before saving. It reports what it found and what it skipped, with the reason — a missing start date, a status that is not approved yet.
One rule worth knowing: leave that is not yet approved does not reduce capacity. A pending request quietly shrinking a sprint would be worse than not tracking it. If your workflow has no approval step, tick Count leave in any status.
Holidays
Team → Public holidays. Paste a whole year rather than adding dates one at a time:
2026-01-01 New Year's Day
2026-04-03, Good Friday
25/12/2026 Christmas DayYYYY-MM-DD or DD/MM/YYYY. American MM/DD/YYYY is rejected rather than guessed at — 03/04 is a different day depending on where you live, and guessing would put a holiday on the wrong date without telling you. Every line it skips is reported with the reason.
Copy a year forward carries fixed dates into the next year. Correct for Christmas and national days; wrong for Easter and anything defined as "the first Monday in May", which need fixing by hand.
Multiple teams
A board is a team. Each board keeps its own roster, leave and holidays, so a project running two squads keeps them separate.
If you used an earlier version where the roster was shared across a project, every board inherits that roster until you first edit it — nothing is lost, and boards diverge only when you deliberately change one. The Team page says when a board is showing an inherited roster.
Portfolio shows several boards side by side, worst first. Someone who works on two boards is counted once in the total: they have one set of working days, not two. The page states how much capacity a naive sum would have invented.
Appearance
Settings → Appearance. Six themes, each with a light and a dark version. The Auto / Light / Dark toggle top-right still applies on top.
This one is personal, not shared — it lives in your browser, not in Jira, so it changes nothing for anyone else. Everything else on the Settings page is shared with the team.
Green, amber and red always mean healthy, warning and over capacity. A theme adjusts those shades to stay readable on its background but never changes what they mean.
Troubleshooting
Everything reads zero, or the numbers look wrong. Wrong estimation field. Settings → Estimation field. The sprint page also banners "N issues have no field value" when it cannot read estimates.
"No boards visible to your account." Either the site has no Software project with a Scrum board, or you cannot browse the projects those boards belong to. The app hides boards you have no permission to open, which is deliberate.
"This board has no sprints." It is a Kanban board. Capacity is measured against a sprint window, so pick a Scrum board.
Someone's leave is not counted. Team → Where leave comes from → Test it. It will say why — usually a missing start date, or a status the workflow has not approved yet.
Saving is refused. Changes need project admin permission on that project. Reading needs only browse.
A holiday and leave on the same day. Counted once. A day already lost to a public holiday is not charged again as annual leave, and two overlapping leave entries cost one day.
Numbers differ between the sprint page and Portfolio. Portfolio de-duplicates people across boards; the sprint page does not, because it is looking at one board. That difference is the point of the page, and it is stated on it.
Getting help
See support. For anything security-related, see the security statement.