Track Team Capacity - Nextedy Documentation

Prerequisites

Planningboard is installed and a board is configured on a Polarion Wiki page.
A teams service is set up for your project. See Set Up Teams Service.
Work items have remaining estimates (or a custom capacity field) populated.
Team members are assigned to work items on the board.

Multi-assignee effort is counted in full, in every rowA work item with more than one assignee appears in each assignee’s swimlane, and its full effort is counted in each one — the effort is not divided between them. Per-user rows can therefore add up to more than the column total, which counts each work item once. Capacity is also calculated from direct task estimates only: effort on sub-items is not distributed upward to parent items.

Enable the teams service

Capacity tracking is switched on for the whole project, not per board. In your project’s administration properties, set:

nextedy.planningboard.useTeamsService=true

This tells Planningboard to pull team membership and calendar data from the teams service rather than using a flat plan capacity value.

Whitespace sensitivityCapacity configuration properties are whitespace-sensitive. Do not add leading or trailing spaces around the = sign or the value. Incorrect whitespace causes silent misconfiguration.

Select the team

The team is chosen by a Polarion page parameter named team on the page that hosts the board. Add it as an enumeration parameter over your team work items; its value is what team and per-user capacity are calculated for. There is no widget parameter for the team. Boards using Enum swimlanes with the resource field set to team take the team from each plan instead.See Set Up Teams Service for how the team, its members and their assignment percentages are defined.

Reload the board

Once the teams service is enabled and the board resolves a team, the capacity bars appear.

Each plan column carries a capacity bar for the team as a whole. This is what capacityLoad switches on.
On a board whose swimlanes are set to Users (Assignee), each user’s swimlane row gets its own bar as well, so you can see at a glance who is over- or under-allocated. This is switched on automatically once the teams service is active and a team is selected — there is no parameter to set.

Show Capacity Load must be onThe capacity bar is drawn only when the board’s Show Capacity Load widget parameter (CAPACITY_LOAD) is enabled. It defaults to off, so a new board shows no bars until you turn it on.

How capacity is calculated

Planningboard derives capacity values from three sources:

Team Calendar and Work Item Estimates feed totalCapacity and allocatedCapacity per user, which combine into the available capacity shown on the board

Value	Definition
`totalCapacity`	Working time available from the user’s calendar for the sprint period, scaled by their assignment percentage on the team. Shown in working days, at eight hours to a day — set `nextedy.planningboard.durationUnit=hours` to show raw hours instead.
`allocatedCapacity`	Sum of remaining estimates for all work items assigned to that user within the sprint.
`availableCapacity`	The part of `totalCapacity` that is not yet planned. It never goes negative: once the planned work exceeds the capacity it reads `0`, and the excess is reported separately as over-planned.

Every figure the board renders is a whole number. A calculated 2.4 displays as 2, and 5.12 displays as 5.

The team total can exceed the sum of the per-user bars. A team assignment that names a department rather than a person contributes to the team’s capacity but has no swimlane and no per-user row, so the difference between the team total and the rows beneath it is that department’s contribution. A user whose only assignment names a department in its resource field keeps a swimlane row but shows zero capacity, because the assignment is charged on the resource side. See Track Department Capacity.

A member with no personal calendar still gets capacityA team member does not need a personal calendar. With no personal calendar and no nextedy.gantt.calendarHolder configured, the member’s capacity is computed from the repository’s default working calendar — measured on three such members, each receiving full capacity for their assignment percentage.nextedy.gantt.calendarHolder does not supply working hours to members who have none — the repository’s base calendar already does that. What it adds is the holder’s non-working days, applied on top of every member’s own calendar.

Apply shared non-working days (optional)

To apply one user’s holidays and shutdown days to everyone, set the nextedy.gantt.calendarHolder property in your project’s administration properties to that user.

nextedy.gantt.calendarHolder = admin

It contributes non-working days only; it is not a working-hours fallback, and members without their own calendar already fall back to the repository’s base calendar.

Configure capacity modifiers (optional)

If your teams have planned capacity reductions — for example, a sprint where the team is partly allocated to a release — enable capacity modifiers:

nextedy.gantt.useTeamCapacityModifiers = true

When enabled, Planningboard reads modifier percentages from the capModA field (default) on each team work item and reduces the calculated capacity accordingly. To use a different field name, set:

nextedy.gantt.capacityModifierAField = <your-field-name>

Verify the capacity display

Reload the board. You should now see:

A capacity bar at the top of each plan column, showing planned effort against the team’s capacity for that sprint.
On a board with user swimlanes, an individual capacity bar in each user swimlane row.
A tooltip when you hover over a capacity bar, with these lines:
- Capacity
- Done
- Todo
- Over-planned — shown in red, and present only when more work is planned than the capacity covers.
- Available — never negative. When the planned work exceeds the capacity it reads 0 and the excess appears on the Over-planned line instead.

For example, a bar with a capacity of 5 and 15 planned reads:

Capacity: 5
Done: 0
Todo: 15
Over-planned: 10
Available: 0

The tooltip describes the bar you are hovering over. It does not break the figures down per user — for per-user figures, read the individual swimlane bars.

Custom capacity tooltipsYou can customize the tooltip content using the columnTooltipTemplate configuration option. This accepts a string template or a function that receives the column and row objects. After updating the template programmatically, call setCurrentView to trigger a re-render.

Example configuration

Team capacity tracking, including the per-user bars, comes from a single project property:

nextedy.planningboard.useTeamsService=true

Everything else follows from the board and its page: the team page parameter decides which team is measured, the swimlane setting decides whether per-user bars appear, and the Show Capacity Load widget parameter decides whether bars are drawn at all.

Limitations

Multi-assignee effort is not divided. A work item with several assignees contributes its full effort to each assignee’s row, so the rows can sum to more than the column total.
No sub-item effort distribution. Parent item capacity is not aggregated from child task estimates; only direct estimates on assigned tasks are counted.
An assignment with % Assignment empty contributes nothing, for people and departments alike.

For troubleshooting capacity values that appear incorrect or zero, see Capacity Calculation Issues.

​Prerequisites

​How capacity is calculated

​Example configuration

​Limitations

​See also

Prerequisites

How capacity is calculated

Example configuration

Limitations

See also