What SAFe integration means in Planningboard
In a standard Planningboard setup, columns represent Polarion Plans and rows represent swimlanes based on assignees, projects, or custom fields. SAFe integration extends both of these axes to reflect the multi-level planning hierarchy that SAFe introduces: Program Increments (PIs), Sprints, Agile Release Trains (ARTs), and Programs within a Solution Train. Rather than treating SAFe-level planning as a workaround involving custom fields and manual queries, Planningboard exposes dedicated plan modes and swimlane assignment types that map directly onto SAFe structures stored in Polarion’s SAFe Solution data. The result is that the planning hierarchy you configured in Polarion’s SAFe module — with its ARTs, teams, and PIs — surfaces on the board without duplicate configuration.The two axes of a SAFe board
Understanding how SAFe integration works requires seeing how SAFe concepts map onto the board’s two independent axes.
- SAFe Sprints in Program (
safeSprints) — SAFe Sprint iterations within a Program (ART level). Plans are loaded automatically using Polarion’s Iteration Plan template; no manual plan query is required. - SAFe Sprints in Portfolio (
safePflSprints) — SAFe Sprint iterations at the Portfolio level, spanning multiple programs in a solution portfolio. - SAFe Program Increments in Program (
safePIs) — Program Increments at the ART (Program) level, showing the 8–12 week PI cadence. - SAFe Program Increments in Solution (
safeSIs) — Program Increments at the Solution level, coordinating PIs across multiple ARTs in a Solution Train.
- Program / Solution Teams (SAFe) (
SAFE_TEAM) — Swimlanes for each SAFe team within the current program, discovered from Polarion’s SAFe Solution data. - Agile Release Train Teams (SAFe) (
SAFE_TRAIN_TEAM) — Swimlanes for teams within a specific Agile Release Train, filtered by ART ID. - Programs (SAFe) (
SAFE_PROGRAMS) — Swimlanes for SAFe programs within a Solution Train, used for portfolio-level planning.
safePIs) columns with Program / Solution Teams (SAFe) (SAFE_TEAM) swimlanes for a classic PI planning view, or use SAFe Sprints in Program (safeSprints) columns with Programs (SAFe) (SAFE_PROGRAMS) swimlanes for cross-program sprint coordination.
How SAFe data is sourced
A critical difference from non-SAFe configuration is where the board gets its data. In Project Plans mode, Planningboard reads plans from the current Polarion project using a Lucene query you supply. In SAFe modes, the board reads from Polarion’s SAFe Solution model — the structured ART, team, PI, and program data managed by Polarion’s SAFe module, not from custom fields you define yourself. This means:- Teams appearing in Program / Solution Teams (SAFe) (
SAFE_TEAM) swimlanes come from Polarion’s SAFe team registry, not from a custom field calledteam. - PIs appearing as columns in SAFe Program Increments in Program (
safePIs) mode are the actual PI plans tracked by Polarion’s SAFe module, not plans matching a user-defined query. - ART filtering in Agile Release Train Teams (SAFe) (
SAFE_TRAIN_TEAM) mode is driven by the ART ID from Polarion’s SAFe configuration, not by a tag or custom field value.
SAFe fields on work items
For SAFe swimlane assignment to work correctly, work items must carry SAFe-specific custom fields that Planningboard reads to route them into the right row. Two field IDs matter:safeTeam— stores the SAFe Team assignment for a work item. Used whenassignmentModeisSAFE_TEAMorSAFE_TRAIN_TEAM.safeProgram— stores the SAFe Program assignment for a work item. Used whenassignmentModeissafePrograms(SAFE_PROGRAMS).
safeTeamField and safeProgramField let you override them.
Capacity configuration parameters and field ID overrides are whitespace-sensitive. A trailing space in a field ID value will cause the field to go unresolved silently. Always trim values when entering them in the widget parameter panel.
Planning hierarchy levels and their configurations
SAFe planning happens at different levels of the hierarchy. The configuration that works at one level does not simply transfer to another — the Plans Mode selection, the swimlane assignment type, and sometimes the portfolio suffix all change.
plans) to SAFe Program Increments in Program (safePIs), the configuration UI in the widget parameter panel changes. Fields that were visible for Project Plans — such as Scope, Query, and Type — are replaced by SAFe-specific fields including the Program Increment Parameter ID field. This is not a UI bug; it reflects that the two modes require fundamentally different inputs. Expecting the same configuration fields across plan modes is a misconception that frequently causes configuration errors.
Selecting SAFe Program Increments in Program (
safePIs) or SAFe Sprints in Program (safeSprints) as the Plans Mode replaces the standard plan query fields with SAFe-specific configuration fields. If you see unexpected or missing fields after switching Plans Mode, this is expected behaviour — check the SAFe-specific parameters rather than looking for the standard plan query fields.Page Parameters and Program Increment Parameter ID
One aspect of SAFe configuration that frequently causes confusion is the use of Page Parameters. In SAFe mode, the board may need to know which specific PI or ART to display — and this information is often passed as a page parameter rather than being hardcoded in the widget. The Program Increment Parameter ID field in the widget configuration references a Page Parameter defined on the Polarion page containing the widget. This indirection exists so that a single board widget can be reused across multiple PIs or ARTs by changing the page parameter value, rather than reconfiguring the widget each time. The setup flow is:- A Page Parameter is created on the Polarion page (not inside the widget).
- The widget’s Program Increment Parameter ID field references that page parameter’s ID.
- The page parameter’s value supplies the actual PI ID or ART ID to the board at runtime.
SAFe-specific swimlane assignment types and support
The KB lists three SAFe swimlane assignment types as available for SAFe environments:- Program / Solution Teams (SAFe)
- Agile Release Train Teams (SAFe)
- Programs (SAFe)
Enabling SAFe swimlane assignment types requires setup guidance specific to your Polarion SAFe Solution configuration. If these swimlane options do not appear in the Assignment Type dropdown of your Planningboard widget, contact Nextedy support for setup assistance — the options require the SAFe Solution to be active and may require additional configuration steps beyond the widget parameter settings.
SAFe sprints: auto-applied plan query
One small but important detail about SAFe Sprints in Program (safeSprints) mode: the plan query is automatically set to filter plans by Polarion’s Iteration Plan template (template.id:iterationPlan). You do not need to — and should not — supply a manual plan query when using SAFe Sprints in Program mode. The auto-applied filter ensures only iteration-level plans appear as columns, preventing PI-level or other plan types from mixing into the sprint view.
This contrasts with Project Plans mode, where the plan query is entirely user-defined.
Common misconceptions
“I can use a customteam enum field instead of the SAFe team field.”
You can use Enumeration Field (ENUM) swimlane assignment mode with a custom team field for non-SAFe team planning, but this is a different configuration from Program / Solution Teams (SAFe) (SAFE_TEAM) mode. The two approaches differ in how teams are discovered (custom enum options vs. Polarion’s SAFe team registry) and in the drag-and-drop behaviour when moving cards between swimlanes. Do not use one as a substitute for the other in a genuine SAFe environment.
“The SAFe plan modes work like Project Plans mode with a pre-filled query.”
SAFe plan modes use Polarion’s SAFe Solution data source, not the standard plan query mechanism. This is why the configuration UI differs: the inputs required are structurally different, not just different query strings.
“Changing Plans Mode just changes which plans are shown.”
Changing Plans Mode also changes the configuration schema the widget expects. Fields available in one mode may not exist in another. Always re-check the widget configuration panel after switching Plans Mode.
“Global enumeration custom fields can be used for SAFe-style swimlanes.”
There is a known limitation: global enumeration custom fields may fail validation after saving in Planningboard swimlane configuration, even if they appear to resolve during initial setup. If you need enum-based swimlanes, use project-scoped enumeration fields. See Swimlane Assignment Modes for the full discussion of field scope requirements.