Capacity
Remaining estimates against working hours, by person or team, after weekends, holidays and leave.
Capacity answers "can we take this on". It compares the work still outstanding against the hours actually available in a range.
How the two numbers are worked out
| Column | How |
|---|---|
| Working days | Days in the range, minus weekends, minus public holidays, minus that person's leave |
| Leave | Their leave days inside the range |
| Available | Working days × hours per day |
| Remaining | Remaining estimate on work items assigned to them that are not done |
| Difference | Available minus remaining — shown as spare time, or as an overrun |
Working days, hours per day, holidays, leave and the team map all come from admin settings. Capacity reads no worklogs at all, so it is cheap compared with a timesheet.
By person or by team
By person gives one row each. By team sums the people in each team, using the team map. Anyone not in the map appears under "No team" rather than being left out.
Unassigned work gets its own row
Work with remaining estimate and no assignee is shown as Unassigned, with no available hours against it. That is usually the most interesting row on the tab: it is the work nobody has picked up, and it is invisible in a per-person view that drops it.
What it does not count
- Work items with no remaining estimate count as nothing, not as zero work. If your team does not estimate, this tab will say everyone has spare time. That is a statement about your estimates, not your capacity.
- Done work is left out entirely, whatever its remaining estimate says.
- Meetings and everything else that is not a Jira work item are not in the available figure. "Hours per day" in admin settings is where to account for that — set it to 6 rather than 8 if two hours a day reliably go elsewhere.
If leave cannot be read, the tab says so — because missing leave makes available hours too high, which is the flattering direction and therefore the dangerous one.