Skip to main content
For the full parameter surface, see the Widget Parameters reference index.

Parameters

Instance and Rendering


Scripting Hook

advScript executes arbitrary JavaScript in the Polarion page context. Incorrect scripts can break board rendering or interfere with Polarion navigation. Test in a non-production environment before deploying.

Item Loading

The default maxItems value of 1000 is a balance between completeness and rendering performance. Boards with hundreds of cards across many swimlanes may feel sluggish; narrow your work-item query rather than raising maxItems.

Example — configuring sidebar fields:
Field IDs must match the exact Polarion field identifiers for your project. Custom fields are referenced by their custom field ID.
sidebarFields sets the default fields presented to all users of this board instance. Per-user customisation (via the gear icon) layered on top is user-scoped and does not affect the widget parameter.

Unplanned Sidebar Hierarchy

Depth trade-offs:
Each additional depth level multiplies the number of parent work items fetched. On large projects with thousands of items, PARAMETER_US_DEPTH values above 2 can significantly increase board load time.

Parameter Visibility and Page Parameters

By default, Planningboard widget parameters are accessible through the gear icon on the embedded widget. There is no built-in option to permanently display the parameter controls above the board without user interaction.
Whether Polarion page parameters ($pageParameters.xxx) can be used to drive Planningboard widget values dynamically is not confirmed in the current source context. Based on ticket evidence, Planningboard swimlane configuration does not support Polarion page parameters for dynamic team filtering — a static workaround (separate Planningboard page per team configured with hardcoded swimlane values) is the supported approach. See Swimlanes (Rows) Parameters for swimlane configuration options.

Configuration Example

The following example shows a widget instance with a unique pbId, a 500-item cap, custom sidebar fields, and an advScript that logs initialisation to the browser console.
Scenario: A sprint Planningboard embedded on a LiveDoc page alongside a Gantt widget. Setting pbId = sprint-board-q3 prevents the two widgets from sharing client state. maxItems = 500 keeps load time acceptable for a project with a large backlog. The sidebar exposes story points alongside the standard fields so planners do not need to open the work item form.

Parameter Interaction Diagram

Diagram mapping each widget parameter (pbId, inView, version, maxItems, sidebarFields, advScript) to its effect on the Planningboard instance

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