Sprint Ledger

Searchable sprint history for Jira Cloud. Sprint Ledger adds five read-only fields to your issues and keeps them up to date, so you can find scope creep, dropped work and carry-over with plain JQL, list columns, dashboards and automation.

The fields

Field	Type	What it holds
Sprint start date	Date	Start date of the issue's current sprint (the active one, else the next planned one, else the last finished one).
Sprint end date	Date	Planned end date of that sprint.
Added mid-sprint	List of sprint names	Sprints the issue was added to after they started, including issues created straight into a running sprint.
Removed mid-sprint	List of sprint names	Sprints the issue was taken out of while they were running. Work moved to the next sprint when a sprint is completed is not counted.
Sprint count	Number	How many started sprints the issue has been part of. A value of 3 means it was carried over twice.

Getting started

Install Sprint Ledger from the Atlassian Marketplace.
Open Jira settings → Apps → Sprint Ledger.
Click Scan history. Sprint Ledger reads each issue's sprint history in the background and fills in the fields for past sprints. New changes are recorded automatically from then on.
Optional: add the fields to your issue screens if you want to see them on the issue view. Search and list columns work without this.

Example searches

Scope added after the sprint started:

"Added mid-sprint" = "Team A Sprint 12"

Work dropped from a running sprint:

"Removed mid-sprint" = "Team A Sprint 12"

Scope added across several sprints:

"Added mid-sprint" in ("Team A Sprint 11", "Team A Sprint 12")

Unfinished work that has been carried over at least twice:

"Sprint count" >= 3 AND statusCategory != Done

Issues in sprints that end this week:

"Sprint end date" >= startOfWeek() AND "Sprint end date" <= endOfWeek()

How it decides

A change within one minute of a sprint starting counts as part of starting it, not as scope creep.
When a sprint is completed, Jira moves unfinished issues to the next sprint. That move is carry-over, so it raises Sprint count but is not recorded as a removal or an addition.
Future sprints are not counted in Sprint count until they start.
Sprint names are stored as text, so renaming a sprint updates the fields the next time any of its issues change, or right away when the sprint itself is edited.

Limits

Each list field holds up to 100 sprint names per issue.
The history scan covers issues that are in a sprint today plus issues updated in the last 365 days (adjustable). Older issues that left every sprint are not scanned.
When a sprint is deleted, its name is removed from the fields of every issue that recorded it.
Jira records the start date you pick in the Start sprint dialog. If you backdate it, changes made between that date and the moment you clicked Start count as mid-sprint.
Dates use your site's default time zone.