Skip to main content
Polarion page parameters ($pageParameters.xxx) are accepted in swimlane row configuration as string values only — manual text entry is required; an enum picker dropdown is not currently available. If string-entry is not sufficient for your use case, create a separate Planningboard page per team and configure row assignment statically. See Configure Swimlanes (Rows) for the available assignment types.

​
Before you start

  • You have a Planningboard widget already embedded in a Polarion Wiki page or LiveDoc.
  • You have edit rights to that page.
  • You know the Polarion page parameter name(s) you want to use (e.g. planId, programIncrement).
1

Identify the widget parameters you want to drive dynamically

Open the widget’s configuration panel (expand tools → click the edit button on the Planningboard widget). The parameters that accept dynamic values are:
For SAFe boards, the Program Increment Parameter ID field is the primary hook for page parameters. Set it to the name of the Polarion page parameter that carries the PI identifier, then the board columns update automatically when the parameter changes.
2

Create or confirm the page parameter on the Polarion page

  1. In the Polarion page editor, open the Page Parameters section (this is a standard Polarion feature, not Planningboard-specific).
  2. Add a parameter with the name you intend to use (e.g. pi).
  3. Give it a default value so the board renders without an explicit parameter in the URL (e.g. the ID of your current PI).
  4. Save the page.
3

Reference the page parameter in the Plans Query

If you are driving which Plans appear as columns, use the Lucene plansQuery in the widget to embed the parameter.Example — filter columns to a specific Program Increment by ID:
Replace pi with your actual parameter name and adjust the field name to match your Polarion configuration.Example — Report Link template for column headers (links each column label to the plan’s own Polarion page):
Capacity configuration parameters are whitespace-sensitive. Ensure there are no leading or trailing spaces around values you paste into the widget configuration panel. A stray space can cause the board to load no plans or miscalculate capacity.
4

Reference the page parameter in the Work Items Query (if needed)

If you also want to filter the work items dataset dynamically, reference the same or a different page parameter in the Query field.Example — show only items planned in the selected PI:
The query property defaults to NOT *:* (no items), so a missing or malformed parameter reference will silently show an empty board. Always define a default value for the page parameter (Step 2) to avoid a blank board on first load.
Each Polarion Wiki page or LiveDoc supports only one Planningboard widget. If you need side-by-side boards (for example, two teams on the same dashboard), create separate pages — one per board — and link them from a hub page. Each page then uses the same parameter name but different default values.
5

Configure the Plan columns count to complement the parameter

When using page parameters to select a PI, you typically want to show all sprints within that PI. Adjust Show # of last plans and Show # of next plans accordingly.From Config.java defaults:
Loading more plans increases the number of work items fetched. The default maxItems limit is 1000. If your board shows blank columns or truncated swimlanes, you may be hitting this limit. Reduce the work items query scope or lower the number of visible plans.

​
Configuration Example

A SAFe Program level board that switches between Program Increments via URL:
Widget — Plans section: Widget — Work Items section: Widget — Swimlanes section:
Flow from the URL ?pi=PI_3_0 parameter into the Polarion page parameter, branching to the Plans Query (columns = sprints inside the PI) and the optional Work Items Query (items filtered to the PI), with a note that swimlane rows stay static

​
Verification

After saving the page with the parameter configured:
  1. Load the page without a ?pi= parameter in the URL — the board should render using the default value you set in Step 2.
  2. Append ?pi=<another_PI_ID> to the URL and reload — the board columns should update to the sprints of that PI.
  3. Hover over a capacity bar — if Show Capacity Load is enabled, a tooltip with load detail should appear.
You should now see the board columns change dynamically as you switch the page parameter value in the URL, with swimlane rows remaining stable.
Planningboard does not support custom Team work item types for swimlane configuration. The product requires Nextedy’s standard Team work item with specific custom fields. If your project uses a custom Team WI type, use Nextedy GANTT (which supports custom team types as of version 25.5.0+) as the primary planning tool, or create a separate static Planningboard page per team using link-role-based rows.

​
See also

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