Sprint Pack help

Views

Sprint Pack shows the same sprint view in four places, plus a portfolio across boards. Everything counts the issues you can see (see whose view is counted), and anyone who can see a board in Jira can use its views.

Where What
A project’s Sprint scope tab The full view for any board in the project
A sprint’s … menu → Scope changes The same view, opened on that sprint
Dashboards → Sprint scope gadget A compact view for one board, or a portfolio
New dashboards → Sprint scope widget The same, with tiles when narrow
Apps → Sprint portfolio Several boards side by side, and any one board’s full view from there

The Sprint scope page

One row per sprint: the active sprint plus the last 6 closed sprints (choose 3, 6, 10 or 15), newest first.

Finding it: under Jira’s new navigation a project shows the Sprint scope tab only once someone adds it with + beside the project’s tabs. Without the tab, the same view is in Apps → Sprint portfolio: a board’s name there opens its view.

No Scrum board in the project: the page says so, since Sprint Pack counts sprints and Kanban boards have none, and links to the portfolio, whose picker lists every board you can see.

Board admins also see a Board settings button at the bottom, here and on the board’s view in the Sprint portfolio, with a count of BI requests waiting. It opens the “BI data for this board” panel: publishing (when allowed), labels, working days, the BI handoff, and the board’s inferred reopens, when it has any. Jira decides who counts as a board admin: space admins on team-managed boards, the board’s administrators on company-managed boards, and Jira admins everywhere.

From a sprint’s menu

On the board’s backlog or sprint, … → Scope changes opens the same view in a dialog for that sprint’s board, with that sprint highlighted and its burndown shown. The sprint is always in the table, even when it’s older than the last 6 closed sprints; while it’s computing, the burndown shows another sprint and switches to it when it’s ready. A future sprint has nothing to show yet.

Dashboard gadget

The Sprint scope gadget puts the view on a Jira dashboard. Its settings choose:

No board is chosen for you. If the list is empty, you can’t see any Scrum board: ask a Jira admin for access to a board’s project and filter. If the boards can’t be loaded, the settings say why and offer Retry.

On a dashboard the table keeps the seven columns that tell the story, with full names: Committed, Taken on, Removed, Scope change, Completed, Say/do and Not done (not completed, with how much was carried over). Re-estimated and Drift are on the board’s Sprint scope page, with every other column. Above the table, the same two-part headline as the page: the last closed sprint, and “Now” for the active one.

The heading names the board, with a link to open it. The answer for the active sprint (or the last closed one), with its goal, is shown above the table. The gadget refreshes with the dashboard, and Refresh reloads it now, in the portfolio too.

Dashboard widget (new dashboards)

On Jira’s new dashboards, the Sprint scope widget shows the same view, with the same settings as the gadget.

“You can’t see this board in Jira” shows when a gadget or widget is set to a board you can’t open in Jira, for example when its filter isn’t shared with you. Nothing about that board is shown. To fix it, ask the dashboard’s owner or a Jira admin for access to the board’s filter and project. The view updates on the next load. The board lists in the settings show only boards you can see. A portfolio says how many of its boards are hidden from you, and leaves them out of its rows and totals.

Reasons for scope changes

Anyone who can see a board can say why an issue was taken on or removed after a sprint’s start. Numbers say what changed; a reason says why, such as “Escalation from support” or “Moved to the next release”, so it travels with the figures when they’re shared.

Work from outside the team

A board’s admins can switch on a guess at which work taken on after a start came from outside the team. It’s off by default, because it isn’t right for every team: some teams work across several projects by design.

Drill-down

Select any count to see the issues behind it and the JQL search that finds them. The list opens directly under the table, headed by the bucket, the sprint and the number of issues, 25 to a page.

Charts

Under the table, four charts, one under another, over the same sprints (computing sprints are left out), each running oldest to newest, left to right (the table runs newest first):

Sprint portfolio

Apps → Sprint portfolio compares boards: each board’s most recent closed sprint, side by side, led by its scope change, with the board’s own average and trend under each figure, each counted as you see it.

Boards differ in size, estimation and kind of work, so the trend compares each board with its own past rather than with the others. A line under the controls says so, with our support address: tell us how you compare boards.

Trend

A trend compares the most recent figure with the board’s own average, for scope change and for say/do separately: “↑ up” more than 5 percentage points above, “↓ down” more than 5 below, “→ steady” within 5. Up isn’t good or bad by itself: a scope change trending up means the plan moved more than usual. Flagged sprints are left out of both sides.

The trend chart (shown when 8 or fewer boards are selected) draws each board’s scope change per closed sprint, or its say/do (the Chart choice above it), counted back from its last closed sprint (“last”, “−1”, “−2” …), oldest to newest. Flagged sprints are left out, as in the table.

Burndown

The What changed tab tells one sprint’s scope story: what changed after its start, who changed it and why, then the burndown, rebuilt from the same list of changes Jira’s burndown chart uses.

Working days

The ideal line runs from the scope at the start to zero at the planned end, flat across non-working days. Jira keeps a board’s working days in a setting Sprint Pack can’t read, so:

Labels

Labels group boards for the portfolio and for BI tools, for example by business line (“Payments”) and by release train (“ART 2”). A board can have several.