What changed after we committed?
Sprint Truth turns Jira's hidden sprint history into plain fields you can search. It puts each sprint on one page for your retro, and checks its numbers against Jira's sprint records every time a sprint closes.
Checked against Jira on every sprint
When a sprint closes, Sprint Truth compares its list with Jira's sprint records and shows the result. Any difference is explained in plain words. How the check works
A Sprint review page
Committed, came in, went out, re-estimated, rolled over and delivered, on one screen, with who and when. See the page
Nine searchable fields
Sprint start, Sprint end, Added after start, Times carried over and more, on every work item. The fields
Sprint 42 at a glance
The Payments team's Sprint 42, as the review page shows it:
✓ Matches Jira's sprint records. 31 + 9 − 4 = 36 work items: 30 delivered and 6 rolled over.
Who it's for
- Scrum masters who need to answer "what came in after we started?" at the retro.
- Delivery managers and PMOs who compare several teams: say/do, scope added after start and rollover rate.
- Jira admins who want sprint dates and sprint history as ordinary fields, with no data leaving the site.
Runs inside Jira
Sprint Truth is built on Atlassian Forge. It makes no calls outside Atlassian, and stores no work item text, names or sprint goals. Security · Privacy