Anyone. Anyone who can see the board. Updated 8 November 2026

Questions people ask about Sprint Forecast and Sprint History

Short answers to the questions people ask first. Anyone can read them, in about 5 minutes.

5 minutes · anyone

Steps

  1. Why is the number different from Jira’s sprint report?

    Jira counts a few things its own way: only the last column is done, work counts at its size when the sprint closes, and its report can use another estimate field. The apps count every item once, at the size it had when it entered the sprint. When the two differ, “Worth a look” says by how much, and “Why” lists each step.

  2. Is this a velocity chart?

    Sprint History’s plan shelf is one, with more in it. Jira’s velocity chart shows two bars per sprint: committed and completed. Sprint History also shows what joined later and finished, and says the result in percent of the plan, so a sprint that took in extra work doesn’t look like a miracle.

  3. How does Sprint Forecast work? Is it a Monte Carlo simulation?

    Yes, in plain form. It takes your last sprints, plays each one’s real daily pace on the work in this sprint, and counts how many would have finished in time. “8 in 10” means 8 of the last 10 did. Epics and releases are replayed the same way. No made-up curve, no dice: your own past.

  4. How accurate is it?

    It is a forecast, not a promise, and it says so on every screen. Under “Past forecasts” it keeps score: what it said each sprint and what happened, for example “Forecasts said about 8 of the last 10 sprints would finish everything. 9 did; Sprint 41 didn’t.” It shows after 5 sprints. If fewer sprints fit than it said, it tells you: “That often means the team changed.”

  5. What happens when nobody estimates?

    Both apps count items instead. They say so on the screen. You don’t need a points field.

  6. What about hours?

    If your team sizes in hours, the apps count hours. Sprint History can also show a points board in hours when enough items have an original estimate. In Sprint Forecast, capacity on an hours board uses the hours of estimate only.

  7. Does it work on Kanban boards?

    Yes. Sprint History tells history by week, and Sprint Forecast gives likely dates for epics and releases. There is no “Will this sprint fit?”, because there is no sprint.

  8. Does it change anything in Jira?

    No. Both apps have read-only permissions. What you try (leaving an item out, moving the cut line, switching a unit) stays on your screen.

  9. Who can see what?

    Everyone sees the boards and work items Jira lets them see. Reads run as the person looking, so there is no way around Jira’s permissions. People views (names, pictures, who has a heavy load) can be switched off by a Jira admin for the whole site.

  10. Does it rank or score people?

    No. “Heavy”, “Usual” and “Light” compare each person with their own usual range, never with each other. There is no leaderboard and no order by performance. Credit for a finished item goes to whoever had it when it finished, and the apps say so.

  11. Why does the forecast say “Too close to call”?

    About half of your past sprints would have finished this plan in time. “What would make it fit” shows which work to leave out to get to your aim, and what keeping everything costs: “Or keep everything: likely needs about 1 more day.”

  12. What does “8 in 10” mean? Can I choose?

    It is how sure you want to be. Choose it with the “Aim for 8 in 10” chip, from “Normal · 6 in 10” up to “A release depends on it · 9 in 10”. A higher aim asks for more days to spare. The sentence under the answer says how many of your past sprints it is based on.

  13. Why doesn’t Sprint Forecast count someone who was quiet for two sprints?

    A person with no finished work for two sprints is left out of the capacity count, so a person on a long leave doesn’t drag your pace down. The “Team” tab shows “Left out: quiet for 2 sprints”, with a “Keep” button to count them anyway.

  14. Can I mark who is away?

    Yes. Choose “Add time off”, or open the “Team” tab and click a day, to mark someone away (whole or half day). Public holidays come from each person’s region. Anyone who can read the board can mark away days. A mark made by someone else shows “Marked by Dev”.

  15. What is in the Free versions?

    Free for one board, with the main answer, the picture, “How it’s counted”, notes, receipts, copying, away days and holidays. The full apps add more boards, dashboard gadgets and a few extras. The plain lists are on “Sprint Forecast: Free and full” and “Sprint History: Free and full”.

  16. Can I put it on a dashboard?

    Yes, in the full apps. Sprint History Free has one gadget, “Velocity chart”, for the Free board.

  17. Do the apps work together?

    They share a look and the same counting rules, but each app keeps its own data. A counting choice in one doesn’t change the other.

If something’s off

  • Your question isn’t here.

    See the troubleshooting guide for Sprint Forecast and Sprint History, or write to support.

Still stuck?

Write to support@unitlane.net. Tell us what you clicked and the exact words you see.

Go to the support page