OVERALL RATINGS
INSTALLS
2
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appJira's Sprint Report as JQL and columns: added after start, removed and carried over, for every sprint you have ever run
Ask Jira what changed after you committed
Nine functions answer in filters, boards, dashboards, automation and subscriptions: added after start, removed, committed, completed, carried over, carried over n times, and the sprints a name or a pattern matches.
Columns, not another report
Ten read-only fields carry each issue’s sprint scope, the dates its sprint started, planned to end and completed, every sprint it was in and how many it rolled through. Sort, filter and subscribe on them.
Say/do and scope creep on every dashboard
The gadget shows committed, added, removed, completed and carried over per sprint, with say/do and scope change, and the CSV export hands the same numbers to Excel, Google Sheets or Power BI, per board or per sprint.
Supporting media
More details
Language: English.
Runs on Atlassian: a Forge app that keeps its ledger in your site’s own Forge storage, in your site’s data residency location, and sends nothing outside Atlassian.
Works with company-managed and team-managed Scrum boards, for sprints that closed years ago as well as the one running now.
Checks itself: the administration page compares any closed sprint with Jira’s own Sprint Report and names the reason for every difference.
Free for sites of up to 10 users.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Sprint Ledger: Sprint Report, Scope Change & JQL for Jira integrates with your Atlassian app
Version information
Version 3.2.0•for Jira Cloud
- Release date
- Oct 8th 2026
- Summary
- A ledger name for each JQL function, a name-clash check and a sprint repair fix
- Details
New: every JQL function also answers under a second name that starts with ledger, such as ledgerAddedAfterSprintStart(), with the same arguments and the same answers. Jira does not guarantee which app answers when two apps register the same function name, and only Sprint Ledger registers the ledger names.
New: when it is installed or updated, and again every day, Sprint Ledger checks whether Jira calls its own functions; the admin page names any function another app answers on the site, with the ledger name to use instead.
Fixed: an issue that leaves a sprint without Jira writing the change into its history, such as an issue turned into a subtask of a parent in another sprint, is now recorded as removed from that sprint when it left.
Changed: two libraries the app is built with are updated for published security advisories.
- Payment model
- Paid via Atlassian
- License type
- Commercial