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

Troubleshooting Sprint Forecast and Sprint History

Find the message you see, and what to do about it. Anyone can use this page, in about 3 minutes.

3 minutes · anyone

Steps

  1. The first read takes a moment

    You see “Reading your last sprints · 3 of 10 · about 20 seconds”. The app is reading your board’s history for the first time. It does this once per board, then keeps it current.

  2. You can leave

    Leave the tab open, or leave and come back: “You can leave. It keeps going.” A normal board takes a few seconds, a big board a couple of minutes. If it takes much longer, Jira may be slow right now.

  3. Jira is busy

    You see “Jira is busy. Showing the answer as of 09:12.” Jira asked the app to slow down. The app shows the last answer it had and the time, and it tries again by itself. Nothing is lost. You can keep reading the old answer.

  4. The app can’t be reached

    You see “Can’t reach the app right now. Showing what it last said.” Your connection or Jira’s app platform dropped for a moment. Choose “Try again” or reload the page. If the message stays for more than a few minutes, check status.atlassian.com.

  5. Couldn’t read this sprint just now

    You see “Couldn’t read this sprint just now” with “Try again”. Choose “Try again”. If it fails again, open “How it’s counted” and then “Notes”: they list anything about the board that stops a reading.

  6. You can’t see the board

    You see “You can’t see this board’s work items, so there’s nothing to show.” Jira doesn’t let you browse the work in that board’s project. A project admin can add you to the project. Choose “Pick another board” to look at one you can see.

  7. A board is missing from the list

    Boards you can’t see in Jira don’t appear. The guide “Settings for Jira admins, privacy and uninstall” explains why.

  8. Only people who can edit can change counting

    You see “Only people who can edit work items in this board’s projects can change this.” Counting rules are saved for the whole board, so they need edit rights. Ask a Jira admin or the project lead.

  9. Nothing finished yet

    You see “Not enough finished work yet” or “Your history starts when your first sprint closes.” The apps learn from finished sprints and give a usual range from 3. Until then they show what exists, marked as rough. “See a sample team” in the ••• menu shows what it looks like with a full history.

  10. The answer says “Too close to call”

    That is an answer, not an error: about half of your past sprints would finish this plan in time, so the forecast won’t pick a side. “What would make it fit” shows what would tip it.

  11. A number is different from Jira’s

    See the guide “How it’s counted”. The “Worth a look” line gives the reason in one sentence.

  12. The numbers changed since yesterday

    In Sprint Forecast, a line such as “Since you last looked (Tue): 2 items added (5 points). 7 in 10 → 5 in 10” says why. “Why” opens “Why it moved” with the full list.

  13. A sprint is missing from the jars

    It was left out of the usual range, and the jar says so: “left out”, with the reason. Sprints with no dates, under an hour long, with no work or on another board are left out. Choose “Include anyway” to see the difference.

  14. A gadget says “Pick a board to show here.”

    Open the gadget’s edit view and pick a board. On a wall display, a dashboard editor has to do it: “Choose a board in this gadget’s settings. If you can’t edit the dashboard, ask someone who can.”

  15. A gadget can’t update

    If the gadget says “Couldn’t update. Showing 06:00”, it couldn’t refresh and shows its last answer, with the time. Choose “Update now”.

Still stuck?

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

Go to the support page