Overview
The Teams Service powers per-swimlane capacity visualization and team-filtered user rows on the Planningboard. It must be enabled both at the widget level (useTeamsService=true) and configured via the properties below before team-based capacity data appears.
Properties prefixed
nextedy.gantt.* are shared between Planningboard and Nextedy GANTT. Changing them affects both products simultaneously.Core Teams Service Properties
nextedy.planningboard.useTeamsService
Enables integration with the Planningboard Teams Service. When
true, the board can retrieve team members, filter user swimlanes by team membership, and calculate per-user and per-team capacity from the team calendar.
When false, capacity values fall back to the plan’s own configured capacity field or remain uncalculated.
Example:
Swimlane Filtering Properties
nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly
When
true, Planningboard shows only users whose Team Assignments overlap with the time range covered by the Plans currently displayed on the board. Users whose assignments fall entirely outside the shown Plan range (only in the past or only in the future relative to the displayed scope) are hidden from user swimlanes.
If a hidden user has work items assigned to them, those items move to the Not Assigned/Other swimlane rather than being lost.
Required data structure:
- A Polarion project with configured Teams and Team Assignments
- Planningboard configured with user-based swimlanes derived from Team Assignments
activeTeamAssignmentsOnly:
This property supersedes nextedy.planningboard.activeTeamAssignmentsOnly (deprecated in 25.12.0). The two properties serve overlapping purposes — enable only one at a time. The recommended property for new configurations is activeTeamAssignmentsInPlanRangeOnly.
nextedy.planningboard.activeTeamAssignmentsOnly
When
true, users with no active (present or future) Team Assignments are hidden from user swimlanes. Users with only past assignments are treated as inactive.
Example:
Capacity Calculation Properties
These properties are shared with Nextedy GANTT and control how team and user capacity is calculated from calendar data.nextedy.gantt.calendarHolder
Specifies a Polarion user ID whose calendar is used as a fallback when a team member has no personal calendar defined. This affects both working-hours calculation and off-days (holidays) determination within the Teams Service capacity engine.
When not set, the system default Polarion calendar applies. Setting a
calendarHolder allows a shared “base calendar” user to represent standard working patterns for the organization.
Example:
nextedy.gantt.useTeamCapacityModifiers
When
true, enables reading capacity modifier fields (capModA, capModB by default) from team work items. These fields hold integer percentages (0–100) that reduce the calculated team capacity proportionally.
This allows modeling scenarios such as overhead, meetings, or partial team availability without changing individual user calendars.
Example:
Capacity modifiers apply to the aggregate team capacity calculation, not to individual user capacity rows. Individual user capacity continues to respect each user’s own calendar and assignment percentage.
nextedy.gantt.capacityModifierAField
Specifies the field ID on team work items that holds the primary capacity modifier percentage. The field must be an integer custom field on the team work item type. The value is treated as a percentage reduction applied to the computed team capacity.
Only read when
nextedy.gantt.useTeamCapacityModifiers=true.
Example:
nextedy.gantt.capacityModifierBField
Specifies the field ID on team work items that holds the secondary capacity modifier percentage. Behaves identically to
capacityModifierAField but represents a second, independent reduction factor (for example, separating planned overhead from unplanned availability reduction).
Only read when nextedy.gantt.useTeamCapacityModifiers=true.
Example:
Property Summary Table
Capacity Calculation Model
WhenuseTeamsService=true, capacity for each user in a Plan is calculated as follows:
allocatedCapacity and availableCapacity are rounded to one decimal place. Users with no calendar entry and no team calendar fallback (nextedy.gantt.calendarHolder) receive totalCapacity = 0.0.
When useTeamCapacityModifiers=true, the aggregate team capacity is further reduced by the modifier percentages read from capacityModifierAField and capacityModifierBField on the team work item.
The exact formula for combining
capModA and capModB (additive vs. multiplicative) is not confirmed in the available source context. Verify the combined modifier behavior against the live product before documenting it in downstream materials.Limitations
- Custom Team work item types are not supported. Planningboard requires the standard Nextedy Team work item structure with its specific custom fields (
from,to, assignment percentage). Unlike Nextedy GANTT (which added support for custom team work item types in 25.5.0), Planningboard does not support custom team types. Projects requiring custom team structures should evaluate whether GANTT is the appropriate primary planning tool. - Page parameters not supported in swimlane configuration. Polarion page parameters (e.g.,
$pageParameters.xxx) cannot be used to dynamically filter team-based swimlanes. Static workarounds include separate Planningboard pages per team or link-role–based swimlane assignment. activeTeamAssignmentsInPlanRangeOnlyrequires a Plan date range. If the displayed Plans have no start/due date, the property cannot determine the active range and falls back to showing all users.
Configuration Example
The following example shows a complete Teams Service configuration for a project using team-based capacity bars and swimlane filtering by Plan range:Related Pages
- Capacity Parameters — widget-level parameters for enabling and displaying capacity bars
- Capacity Properties — system-wide capacity calculation configuration
- Teams Service API — scripting interface for reading team and capacity data
- SAFe Team Mode — swimlane assignment by SAFe team
- Assignee Mode — swimlane assignment by individual user
- Configuration Properties — index of all administration configuration properties
Sources
Sources
KB Articles
- Planningboard: Customizable Statistics and Capacity Indicators
- Planningboard Widget Parameters
- Filter user swimlanes by Plan range
PlanningBoardDataService.javaIPlanningBoardTeamsService.javacapacityHelperData.cy.tsConfig.javaPlanningBoardTeamsService.java