SAFe Team Mode requires a configured Polarion SAFe Solution project hierarchy. The board must reside in a program-level project that is part of a SAFe portfolio structure. Contact Nextedy support for initial setup guidance.
Overview
WhenassignmentMode is set to Program / Solution Teams (SAFe) (SAFE_TEAM), Planningboard discovers all team-level projects within the current SAFe portfolio and renders one swimlane per team. Work items are assigned to swimlanes based on the value of the safeTeam custom field (configurable via safeTeamField).
safeTeam field to the target team.
Widget Parameters
Configure SAFe Team Mode in the Swimlanes (Rows) section of the widget parameters panel. See Swimlanes (Rows) Parameters for the full swimlane parameter reference and SAFe Parameters for SAFe-specific parameters.Assignment Mode Parameter
SAFe Team Mode Parameters
Swimlane Sort Values
Additional
swimlaneSort values beyond alphabetical may be available. Verify the full set of accepted values in the widget parameter panel of the running application.Relationship to Other SAFe Assignment Modes
Planningboard provides three SAFe-specific assignment modes. Choose the correct mode based on the planning level:
Use SAFe Team Mode when the board is embedded in a program-level project and you want all teams in that program to appear as rows. Use SAFe Train Team Mode if you need to scope rows to a specific ART by ID.
Configuration Example
The following example shows a Planningboard widget configured with SAFe Team Mode for program-level sprint planning. Plans columns display SAFe sprints (plansMode = SAFE_SPRINTS) while rows show teams in the current ART.
How Team Discovery Works
When SAFe Team Mode is active, Planningboard uses the Polarion SAFe Solution project hierarchy to identify teams:- The board’s host project is identified as a program-level project within a SAFe portfolio.
- All team-level projects (
getTeamProjects()) within the same portfolio are retrieved. - One swimlane is created per team.
- Work items are matched to team swimlanes via the
safeTeamFieldcustom field value.
Work Item Assignment Behavior
SAFe Parent Sync
When a work item’s team assignment changes (by drag-and-drop), Planningboard automatically syncs the User Story to the correct Team Program Increment plan. ThissyncSAFEParentsFromChildren behavior ensures that plan membership stays consistent with team assignment without requiring manual updates. Plan IDs are remapped based on the new team assignment.
Capacity Behavior
When capacity tracking is enabled alongside SAFe Team Mode, capacity bars appear per team swimlane. Capacity is aggregated at the team level across the displayed Plan columns.
See Capacity Parameters and Teams Service Properties for full parameter details.
Filtering Active Teams by Plan Range
When swimlanes are derived from Team Assignments via the Teams Service, you can restrict displayed team rows to those with active assignments within the time range of the currently shown Plans. Enable this in Administration > Configuration Properties:- Teams with no assignments overlapping the displayed Plans’ date range are hidden.
- Work items assigned to hidden teams move to the Not Assigned / Other swimlane.
nextedy.planningboard.activeTeamAssignmentsOnly=true was the earlier variant (introduced in 25.3.0). It filtered only past assignments, independent of the shown Plans’ scope. It was deprecated in version 25.12.0 in favor of activeTeamAssignmentsInPlanRangeOnly.Required Data Structure
For SAFe Team Mode to function correctly, the Polarion environment must have:- A SAFe Solution project hierarchy (portfolio → program → team projects).
- The board’s host project configured as a program-level project within that hierarchy.
- A custom enumeration field (default:
safeTeam) present on the work item types shown on the board. - Work items populated with
safeTeamfield values matching the team project identifiers.
useTeamsService=true), also configure:
- Teams and Team Assignments within each team project.
- The Teams Service properties in Administration > Configuration Properties (see Teams Service Properties).
Limitations
- No sub-item effort distribution: Capacity is tracked at the team swimlane level only. Effort is not automatically distributed across individual team members or child work items.
- No multi-assignee capacity: SAFe Team Mode does not split capacity across multiple team assignments on a single work item.
- Swimlane sort is fixed to alphabetical: Only alphabetical sort order is confirmed for team swimlanes. Sort options available for other assignment modes (such as Assignee Mode) may not apply.
- SAFe hierarchy required: The mode produces no swimlanes if the host project is not part of a recognized SAFe portfolio structure. No error is surfaced; the board renders with no rows.
- Configuration UI changes with Plans Mode: The widget parameters panel shows different configuration fields depending on the selected Plans Mode. SAFe-specific configuration fields (including PI increment selection) appear only when a SAFe plans mode is active. See SAFe Parameters.
Related Pages
- Assignment Modes — Overview of all assignment modes
- SAFe Train Team Mode — Scope teams to a specific ART by ID
- SAFe Programs Mode — Portfolio-level program swimlanes
- Swimlanes (Rows) Parameters — Full swimlane parameter reference
- SAFe Parameters — SAFe-specific widget parameters
- SAFe Sprints — SAFe sprint columns (typical pairing with SAFe Team Mode)
- SAFe Program Increments — PI-level columns
- Teams Service Properties — Teams Service configuration
- Capacity Parameters — Capacity tracking configuration
Sources
Sources
KB Articles
- Swimlane Assignment Types
- What is ‘Normalization’
- Filter user swimlanes by Plan range
PlansMode.javaPlanningBoardWidgetRenderer.javaPlanningBoardDataService.javaAssignmentMode.javaPlanningBoardWidgetDependenciesProcessor.java