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

How it’s counted: planned, finished, joined later, taken out

Every number in both apps comes from the same few rules, and you can read them. Anyone can open them, in about 5 minutes.

5 minutes · anyone who can see the board

Steps

  1. Open the rules

    Choose “How it’s counted” in the bar under the header of either app, or in the ••• menu. It lists the rules in plain lines: “Counting”, “Finished”, “Sizes”, “Subtasks”, “The plan”, “History”, “Holidays”, “Left out” and “No estimate”. When your board matches Jira’s defaults, it says “Matches Jira’s way”.

  2. See what is in each count

    A number can be opened to see which work items are in it (“Counted”) and which are not (“Left out”).

  3. Planned at the start

    The plan is the work items that were in the sprint at the moment it started, each at the size it had when it entered the sprint. Work that joined later is not in the plan. Work that was taken out before the sprint closed stays in the plan, the way Jira’s report treats it.

  4. Finished

    An item counts as finished when it sits in a finished column when the sprint closes. The finished columns are the last column by default, and you can choose them. An item that was reopened before the sprint closed is not finished. An item that was already done when it joined the sprint adds nothing.

  5. Joined later

    Work that joined the sprint after it started. If it finished, it shows as a dotted block on top of the jar. If it did not, it shows in “Joined later, not finished”. Joined-later work is never counted as if it had been planned.

  6. A planning window

    If your team plans for an hour or two after the start, set a “Planning window” and those items count as planned.

  7. Taken out

    Work that left the sprint before it closed. It stays in the plan, so a sprint that drops half its work does not look like a success. You see it hatched in the jar, and by name in the sprint’s list.

  8. Not finished

    Work that was in the plan and was not finished when the sprint closed. Most of it moves to the next sprint. It shows as the empty part of the plan outline.

  9. Resized

    Everything counts at the size it had when it entered the sprint, not at the size it grew to. A 3 that became an 8 mid-sprint counts as a 3, and the sprint says “Resized from 3 to 8”. That is why a team that quietly re-estimates upward can’t make its numbers look better.

  10. Left out on purpose

    Some work never counts: sub-tasks (their parent counts, as in Jira), work items marked “Won’t do”, epics, and anything your team has left out. Every item that isn’t counted shows its reason, for example “Sub-task: its parent counts” or “Left out by your team”.

  11. No estimate

    An item with no estimate counts at your team’s usual size, never as 0, and the note says so: “This counts 2 unestimated items as 3 points each.” If one such item decides the answer, the note shows both outcomes. You can pick a fixed size to use for them, or count items instead of points.

  12. The usual range

    “Usual” is the middle of your last sprints with the highest and the lowest left out, so one freak sprint doesn’t move it. “Sprints used” in “Settings” sets how many. A sprint is left out, and says why, when it has no dates, ran under an hour, had no work, finished nothing, or belongs to another board.

  13. Why this can differ from Jira

    Jira’s sprint report counts differently in a few places: it counts only the last column as done, it can use a different estimate field, and it counts a work item at the size it has when the sprint closes. Your team’s own choices can add more.

  14. The “Worth a look” line

    When the app’s number differs from the number Jira likely shows, the “Worth a look” line says so, for example “Jira likely shows 36 for Sprint 46; this count is 34.” Choose “Why” to see each step. An app can’t read Jira’s own report, so this is the number its rules should give.

  15. Change a rule

    Choose “Settings” in the ••• menu. The rules sit under “How to count”: “Finished”, “Sizes”, “Subtasks”, “Planning window”, “Sprints used”, “Counted since” a date, “Public holidays”, “Left out” and “Items with no estimate”.

  1. Preview, then save

    “What counts” can narrow the board to a quick filter, a component, a label or a team. Change a choice, like the aim “Careful · 7 in 10”, and a bar shows the result first: “With this change: Likely needs about 9 more days.” Choose “Use this” or “Cancel”. After saving, “Undo” appears. “Back to Jira’s way” puts everything back.

  2. Who can change it

    Only people who can edit work items in the board’s projects can change a rule, and a change is the same for everyone on that board in that app.

If something’s off

  • A number is different from Jira’s report.

    Open “Worth a look”, then “Why”. It lists the differences, one per row.

  • An item you expected is missing.

    Open “How it’s counted” and look at “Left out”. Each item shows its reason.

  • A sprint isn’t in the usual range.

    Its jar says “left out” and why, for example “nothing finished” or “ran in parallel”. Choose “Include anyway” to see the difference.

  • You can’t change a rule.

    You see “Only people who can edit work items in this board’s projects can change this.” Ask a Jira admin or the project lead.

Still stuck?

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

Go to the support page