Parameters
Instance and Rendering
Scripting Hook
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.Sidebar Fields
Example — configuring sidebar fields:
Unplanned Sidebar Hierarchy
Depth trade-offs:
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 uniquepbId, a 500-item cap, custom sidebar fields, and an advScript that logs initialisation to the browser console.
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
Related References
- Widget Parameters — full parameter index
- Work Items Parameters — query, sort, and dependency configuration
- Plans (Columns) Parameters — plan type, count, and column link
- Swimlanes (Rows) Parameters — assignment types and row configuration
- Scripting API — JavaScript API available to
advScript - Config Script API — configuration scripting reference
Sources
Sources