Sprint Pack help

How the numbers are counted

Sprint Pack counts each sprint the way Jira’s Sprint Report does, from each issue’s history. This page defines every number, says whose view it counts, and lists the cases where a number is less certain.

The same definitions apply on every surface: the Sprint scope views, the exports, the slides, the Sprint portfolio and the published BI data.

Whose view is counted

Each view counts the issues the person looking at it can see. Two people with different permissions can see different numbers for the same sprint.

Surface Counts Label
Sprint scope views (project page, sprint menu, dashboard gadget and widget), the Sprint portfolio Issues the viewer can see “Counted as you see them”
Exports, slides, the copy summary, snapshots Issues the person who made the file could see “As visible to you on ", or "Counted as "
Published BI data (board properties) Issues the app can see countedAs: "app"
BI issue lists (script --issues, Sheets Issues tab) Issues the reader’s credential can see countedAs: "reader"

Parity with Jira’s Sprint Report

The scope view matches Jira’s Sprint Report as you see it, as long as Sprint Pack can see every issue on the board.

What makes the numbers match:

When the numbers can differ:

Hidden issues: ones you can’t see

Issues you don’t have permission to view are left out of your counts. Jira’s Sprint Report leaves them out for you too.

Issues the app can’t see

An issue with a security level that leaves Sprint Pack out isn’t counted anywhere in Sprint Pack: not in the views, the exports or the published totals.

The buckets

Every sprint is split into the same buckets. Each is a Jira search you can open (see the JQL functions).

Bucket In short Short header (dashboard)
Committed In the sprint when it started Start
Taken on Taken on after the start Add
Removed Removed after the start Rem
Completed In the last column at close Done
Not completed Still in the sprint at close, not in the last column Open
Carried over Not completed and moved to a later sprint Carry
Re-estimated Estimate changed during the sprint Re-est

Two more appear in files and BI data:

An issue can be in several buckets: taken on and completed, or committed, not completed and carried over.

Counts and points. Every bucket has an issue count and, on a board with estimates, a point total. Points use the estimate at a fixed moment:

Bucket Estimate taken
Committed At the start (also for issues removed later)
Taken on When first taken on
Removed At the start for committed issues, when taken on for the others
Completed, not completed, carried over At the close (the current value while the sprint is active)

Committed

Issues in the sprint at its start, except issues already in the board’s last column then.

Taken on after the start

Issues that joined the sprint after its start and before its close (or now, while it’s active): requests the team took on once the sprint was under way.

Exports, BI data, the addedAfterSprintStart() function and the Jira field “Added after sprint start” still call it “added” (issues_added, addedAt), so files and searches you already use keep working.

Removed

Issues that left the sprint after its start and were still gone at the close.

Completed

Issues in the board’s last column at the sprint’s close, inside the board’s filter.

Not completed

Issues still in the sprint at its close and not in the board’s last column then. While the sprint is active: in the sprint and not in the last column now.

Carried over

Issues not completed at the close that are in a later sprint on the same board: one that started after this sprint, or a future sprint.

Re-estimated

Issues whose estimate, on the board’s estimation field, changed while they were in the sprint: between the start (or the moment they were taken on) and the close.

Drift

Drift is how much the sprint’s estimates moved: the estimate at the close minus Jira’s value, summed over the sprint’s work.

Unestimated at the start

An issue with no estimate at the start (or when it was taken on) is its own category, never an infinite percentage.

Say/do

Say/do = completed from the commitment ÷ committed. It answers “of what we committed to at the start, how much did we finish?”

Scope change

Scope change = (taken on + removed) ÷ committed. It can be well over 100%.

A big scope change is never flagged as an anomaly.

Velocity

The velocity chart shows, per sprint, what was committed at the start, how much of that was done, and how much work taken on after the start was done. The last two add up to completed, the bar in Jira’s velocity chart.

Velocity ratio

Velocity ratio = completed ÷ committed. Unlike say/do it includes work taken on after the start that was completed, so it can be over 100%. It’s the ratio behind Jira’s velocity chart.

Carry-over rate

Carry-over = carried over ÷ (committed + taken on). The share of the sprint’s work that moved to a later sprint.

Averages across sprints (in the portfolio and BI marts) are ratios of sums over the selected closed sprints: a small sprint doesn’t weigh as much as a full one. Across boards, see units.

Approximate (≈)

“≈” marks a count that may be slightly off because Sprint Pack didn’t see the sprint close.

Computing

“Computing” means one thing everywhere: Sprint Pack hasn’t yet computed this sprint under its current rules.

History refreshing

The burndown needs each issue’s sprint and status history. For issues Sprint Pack recorded before it kept that history, the burndown uses the moments it already knows (when the issue was taken on or removed) and its current status instead.

When a board’s estimation changes

When a board’s estimation field changes, Jira recalculates every past sprint with the new field, and so does Sprint Pack.

Board settings Sprint Pack can’t read

If Sprint Pack can’t read a board’s settings, it doesn’t know the board’s columns, so nothing counts as completed and the totals are not Jira’s.

Done at the start

An issue already in the board’s last column when the sprint started is, in the Sprint Report’s words, “completed outside of this sprint”.

Sub-tasks

Sub-tasks are left out of every count and every JQL function, as Jira’s Sprint Report and burndown leave them out. A sub-task belongs to its parent’s sprint.

Units

A board estimates in one of three ways, and every point total is in that board’s unit:

The toggle on each view switches between issue counts and the board’s estimates.

Across boards (the portfolio, slides, BI marts):