Skip to main content

Plans Mode Selection

The plansMode parameter is the primary switch for SAFe integration. Setting it to a SAFe value changes which additional configuration fields are shown and which Plans are loaded as columns.

Available SAFe Plans Mode Values

When plansMode is set to a SAFe value, the widget parameter editor shows different fields than it does for Project Plans. In particular, the Scope, Query, and Type fields present under Project Plans are replaced by SAFe-specific fields. If you see an unexpected configuration UI, verify your Plans Type selection first.
Configuration fields shown for each plansMode value: Project Plans shows Scope, Query Type, Query, Sync to Parent Plan, and Plan Link; SAFe Sprints in Program/SAFe Sprints in Portfolio shows the Program Increment Parameter ID and hides Sync to Parent Plan and Plan Link; SAFe Program Increments in Program/SAFe Program Increments in Solution shows only the Program Increment Parameter ID

SAFe Program Increment Parameter

This parameter is shown only when Plans Type is set to SAFe Sprints in Program (SAFE_SPRINTS) or SAFe Sprints in Portfolio (SAFE_PFL_SPRINTS).
The Program Increment Parameter ID field references a Polarion page parameter by name — it does not create one. You must define the page parameter on the Wiki or LiveDoc page first, then enter its ID here. If the parameter is missing or the ID is wrong, no plans load. See the ticket insight: SAFe configuration errors most commonly trace back to missing or misreferenced Page Parameters.

Assignment Mode — SAFe Swimlanes

These parameters control how swimlanes are grouped when using a SAFe assignment mode. Set assignmentMode to one of the SAFe values to activate SAFe-based row grouping.

SAFe Assignment Mode Values

SAFe Assignment Mode Parameters

The values of safeTeamField and safeProgramField must exactly match the custom field IDs in your Polarion project, including casing. A mismatch produces empty swimlanes with no error message.

SAFe Plan Cells Mode

When using SAFe sprints or stemming-based planning, items can be locked to specific plan-resource intersections (cells) rather than moved freely across plans.
The exact runtime behavior of planCellsMode in each SAFe plans mode combination should be verified against the live product, as interactions between planCellsMode, plansMode, and assignmentMode are complex.

SAFe Parent Sync

When work items are assigned to a team in a SAFe mode, Planningboard can automatically sync those items to the correct Team Program Increment plan.
The syncSAFEParentsFromChildren behavior — automatically syncing SAFe User Stories to the correct Team Program Increment plan when team assignment changes — is an automatic behavior in SAFe plans modes, not a separately configurable parameter. It triggers when a work item’s team assignment changes and remaps the plan ID based on the team assignment.

Capacity Parameters in SAFe Contexts

Capacity calculation parameters apply in SAFe modes as in standard modes, but their interaction with SAFe plan structures has specific behavior. See Capacity Parameters for the full capacity configuration reference.

Configuration Example

The following example shows a board configured for SAFe Program Increment planning at the program level, with teams as swimlanes.
This configuration produces a board where:
  • Columns are SAFe iteration plans (sprints) within Program Increment PI_2025_Q3
  • Rows (swimlanes) are SAFe teams sourced from the Polarion SAFe Solution
  • Only teams with assigned cards are shown (showEmptySwimlanes = false)
  • Capacity bars are shown per swimlane per sprint
For a portfolio-level board showing Programs as swimlanes across Solution Train PIs:

Level-by-Level Configuration Summary

Different SAFe hierarchy levels require different combinations of plansMode and assignmentMode.
SAFe hierarchy levels — Portfolio, Program PI Planning, Program Sprint Planning, and Portfolio Sprint Planning — with the recommended plansMode, assignmentMode, and field configuration for each level

Limitations

  • Planningboard swimlane configuration does not support Polarion page parameters (e.g. $pageParameters.xxx) for dynamic team filtering. Workarounds include configuring static swimlanes using link roles, or creating one Planningboard page per team.
  • Custom Team work item types are not supported for SAFe swimlane configuration. Only Nextedy’s standard Team work item type with the required custom fields (safeTeam, safeProgram) is supported. Nextedy GANTT (25.5.0+) supports custom team types if that is a requirement.
  • SAFe configuration is highly context-dependent: the configuration UI changes based on plansMode selection. If your board is showing unexpected configuration fields, verify the Plans Type selection first.
  • Multi-assignee capacity distribution and sub-item effort distribution are not supported in SAFe modes (consistent with general Planningboard capacity limitations vs. Nextedy GANTT).

KB Articles
  • Planningboard Widget Parameters
  • Planningboard: Customizable Statistics and Capacity Indicators
  • Planningboard interface & basic interactions
Support TicketsSource Code
  • Config.java
  • PlanningBoardWidget.java
  • widget.vm
  • PlanningBoardWidgetRenderer.java
  • PlanningBoardWidgetDependenciesProcessor.java
Last modified on July 10, 2026