Frequently asked questions
Updated 8 October 2026
Using it
- What does Sprint Ledger do?
- It rebuilds the history of every sprint your Jira site has run, from the history Jira keeps for each issue, and keeps it current. You get the answers as JQL functions (
issue in addedAfterSprintStart("Sprint 42")), as fields you can show as columns, as a dashboard gadget and as a CSV export: what was committed, what was added after the start, what was removed, what was completed and what carried over.
- Jira has a Sprint Report. Why is that not enough?
- The Sprint Report shows one sprint at a time, as a page. It cannot be searched, filtered, put in a column, used in an automation rule or exported for every sprint at once, which is what a retrospective across teams or a quarterly report needs. Sprint Ledger answers the same questions in JQL, so they work everywhere JQL works.
- Why do some numbers differ from the Sprint Report?
- Seven differences are expected. The commonest: subtasks are left out by default, as in the report; an issue added after the start and then removed counts as both added and removed, where the report lists it once; an issue that has since left the board's filter drops out of the report and stays in the ledger; and "completed" follows the board's current columns, which matters for an old sprint if the columns were rearranged since. An issue that was already done when the sprint started is completed outside the sprint in both, as Jira counts it. How Sprint Ledger counts explains all seven, and the admin page's Compare with Jira's Sprint Report checks your own sprints against the report in one step. Any other difference is a bug we want to hear about.
- Why does an issue have this value?
- Open the issue and add the Sprint history (Ledger) panel from the apps button under its title. It lists every sprint the issue has been in, with the reason for each tag: when the issue entered and left the sprint, and the status it had when the sprint closed (more).
- Does it cover sprints from before it was installed?
- Yes. The first reconstruction reads the history of every issue that has been in a sprint, so a sprint closed years ago is answered like last week's, as far back as Jira's history for your issues goes.
- Can I use the functions in automation rules and saved filters?
- Yes: anywhere Jira takes JQL, including automation conditions, board filters, dashboard gadgets and filter subscriptions. Jira stores a function's answer and reuses it; the app updates those stored answers when sprints start, complete or are renamed, and daily. See Saved filters, boards and automation.
- Another app has a function with the same name
- Jira does not guarantee which app answers when two apps register the same JQL function name. Sprint Ledger checks every day whether Jira calls its own functions, and the admin page names any that another app answers. Every function also answers under a name only Sprint Ledger registers, with
ledger in front: ledgerAddedAfterSprintStart() instead of addedAfterSprintStart(), and so on. More on the functions page.
- A saved filter says "Field ... does not exist"
- The fields were renamed in September 2026, and Jira does not rename fields inside saved queries. Replace the old name with the new one from the table of names.
- Does it work with team-managed projects?
- Yes, with the same functions, fields, gadget and export. Columns and JQL work with no setup; to see the fields on the issue view, add them on the project's Fields page (how).
- Does it work with Kanban boards?
- A Kanban board has no sprints, so there is nothing to reconstruct; the app lists such a board as "no sprints" and skips it.
- Is there a version for Jira Data Center?
- No. Sprint Ledger is built on Atlassian Forge, which runs on Jira Cloud only.
Installing and running it
- Does it change my issues?
- Only its own ten read-only fields, which nobody else can edit. It writes them without adding entries to the issues' history, and it never changes summaries, statuses, sprints or any other field.
- Where is my data, and does anything leave Atlassian?
- Nothing leaves Atlassian. The app runs on Atlassian's infrastructure, stores its records in Forge storage attached to your installation, in your site's data residency location, and makes no calls to any other service. It stores IDs, dates and the values it computes, never summaries, descriptions or comments. See the privacy policy and security.
- Who can see what?
- Searches return only issues the person searching can see. The admin page is for Jira administrators, the project settings page for the project's administrators, and the gadget and the export show a board's numbers only to people who can see the board.
- What does it cost my site's API budget, and how long does the first reconstruction take?
- About two Jira API points per issue that has ever been in a sprint, at most 12,000 points an hour by default: a few minutes for a small site, about two hours for 10,000 such issues, a working day for 50,000. Afterwards the app runs on Jira's events, which cost nothing, plus an hourly check of a point or so per active sprint. The budget can be changed on the admin page.
- A board is missing
- Jira shows a board to an app only when the app can see the board's filter. Share the filter with the project or with everyone logged in (Filters → the board's filter → Details → Edit permissions), then press Rebuild every tracked board on the admin page.
- The fields are empty on the issue view
- Either the project is turned off on the admin page, or the fields are not on the issue layout yet. If they have values as columns in the issue search, it is the layout: add the fields.
- The reconstruction seems stuck
- It pauses when the hourly API budget runs low and resumes within the hour, so a still progress bar is normal on a large site. If nothing has moved for more than an hour, tell us.
- What happens if I uninstall?
- The fields disappear from Jira at once. Atlassian keeps the data for about a month so that a site that uninstalled by mistake can recover it, then deletes it. Details in the privacy policy.
Price and support
- What does it cost?
- Sites with up to 10 users use it free. Larger sites subscribe through its Atlassian Marketplace listing, which shows the price, after Atlassian's usual free trial. Sites that installed during the private beta keep every feature without a subscription until 31 December 2026.
- How do I install it?
- From its Atlassian Marketplace listing, as a Jira administrator: pick the site, review the permissions and install. Getting started says what happens next.
- How do I get help?
- Email support@dyordanov.com. The support page says how fast you get an answer and what to include.