Sprint Ledger for Jira

Sprint scope change and carry-over as JQL and columns, for every sprint you have ever run.

Ask Jira what was added after you committed, what was removed, what was completed and what keeps rolling over: issue in addedAfterSprintStart("Sprint 42"). Sprint Ledger rebuilds each sprint from the history Jira already keeps, so it answers for sprints that closed years ago as well as for today's, and it runs entirely on Atlassian's infrastructure.

Sprint Ledger is on the Atlassian Marketplace for Jira Cloud: install it from its listing. Sites with up to 10 users use it free; larger sites start with Atlassian's free trial.

Documentation

• Getting started: install, the first reconstruction, two things to check, and comparing the numbers with Jira's Sprint Report.
• JQL functions: the nine functions, their arguments and patterns, the messages they give, and examples.
• Fields: the ten read-only fields, as columns, in JQL and on the issue view.
• Dashboard gadget: committed, added, removed, completed and carried over per sprint, with say/do and scope change.
• CSV export: a board's sprints or one sprint's issues, for Excel, Google Sheets and Power BI.
• How Sprint Ledger counts: the definitions, the awkward cases, and the differences from the Sprint Report.
• Administration: projects, boards, settings, the API budget, updates, troubleshooting and uninstalling.
• FAQ, changelog and support.

Articles

• Four ways to find issues added after sprint start in Jira Cloud (2026): the Sprint Report, an automation rule, Appfire's JQL Search Extensions and Sprint Ledger compared, and when each is enough.
• How to find issues removed from a sprint in Jira Cloud (2026): why JQL cannot search the Sprint field's history, and the Sprint Report, an issue's history, the report's endpoint, an automation log and Sprint Ledger compared.
• Sprint start and end dates in JQL and as columns (Jira Cloud, 2026): Jira's sprint functions, automation into date fields, a sprint-fields app and Sprint Ledger compared.