Parameter overview
Sidebar fields
When a user clicks a card, the Work Item Properties sidebar opens on the right. The fields shown there are controlled by thesidebarFields parameter.
Behavior
- The default value is an empty array (
[]). When no fields are configured, the sidebar falls back to application-level defaults (confirmed astitle,status, andplannedInfrom the source). - Users can additionally personalize their own sidebar view via the Select Fields button (gear icon) inside the sidebar — this is per-user, per-work-item-type, and does not override the widget parameter.
- Saving changes in the sidebar preserves the user’s swimlane position and scroll location; the board does not jump back to the top.
Configuration example
Use the exact Polarion field ID as it appears in project configuration. Wrong casing fails silently — the field is omitted from the sidebar without an error message.
Board rendering mode
Notes on inView
- In view mode the board is rendered inside an iframe with a modal editor overlay for parameters.
- If a page hosts only one Planningboard widget,
inViewcan remainfalse.
Notes on pbId
- When two or more Planningboard widgets appear on the same LiveDoc or Wiki page, each must have a distinct
pbIdvalue. - The value is appended to the iframe
srcURL and used in DOM element IDs.
Configuration example
Dependency visualization
The Show Dependencies toolbar button reveals dependency arrows between cards. The arrows are drawn only for the link roles configured here.Behavior
- If
dependencyLinkRolesis not set, the Show Dependencies toolbar button has no effect — no arrows are drawn. - The card-level Show Links quick action (hover over a card) uses the same link role to highlight related cards and hide unrelated ones.
- Setting this parameter also enables the Add Link quick action on cards.
Configuration example
Unplanned sidebar hierarchy
The Unplanned section on the right of the board shows cards not yet assigned to a Plan. For team leads and project managers working with feature hierarchies, the sidebar can load parent items to provide context.Behavior of usDepth
- A value of
0or leaving the parameter unset shows only the work items themselves, with no parent context. - A value of
1loads the immediate parent of each unplanned item. - Higher values load deeper ancestors but increase the number of API calls. On large boards with many unplanned items, deep hierarchies may noticeably increase load time.
Behavior of parentsLinkRole
- Set this to the link role that defines the parent relationship in your Polarion project (for example,
parentoris_parent_of). - If left unset, no parent hierarchy is loaded regardless of the
usDepthvalue.
Configuration example
Version and cache busting
The
version parameter is managed automatically by the Planningboard plugin. It is listed here for completeness. Do not set it manually in widget parameters.Advanced script execution
Usage notes
- Intended for advanced customization scenarios only. Consult the Scripting API and Config Script API for the available scripting surface.
- Incorrect scripts may break board initialization. Test in a non-production environment before deploying.
- Do not expose sensitive data in script content — the value is embedded in the page HTML.
Configuration example
Configuration example — complete UI parameters block
The following example shows a representative configuration for a sprint Planningboard used by a single Scrum team. Iterations are columns, assignees are swimlanes. The sidebar shows key fields, dependencies use thedepends_on link role, and parent context is one level deep in the unplanned sidebar.
Toolbar controls reference
The following toolbar controls are affected by the UI parameters described on this page. See Toolbar Controls for the full toolbar reference.Known limitations
- Parameter visibility: There is no built-in option to display widget parameters permanently above the board without clicking the gear icon. Parameters are only accessible through the standard Polarion widget parameter editor. There is no confirmed workaround for permanently exposing parameters above the widget.
- Sidebar fields per work-item type: The
sidebarFieldsparameter applies globally to all work item types shown on the board. Per-type sidebar field sets are not supported at the widget parameter level; individual users can add type-specific fields using the gear icon inside the sidebar, but these additions are user-local.
Related pages
- Widget Parameters — overview of all parameter groups
- Work Items Parameters — query, sort, and type filters
- Capacity Parameters — capacity bar configuration
- Swimlanes (Rows) Parameters — swimlane assignment types
- Toolbar Controls — toolbar button reference
- Unplanned Sidebar — unplanned section reference
- Card Quick Actions — hover actions on cards
- Scripting API — advanced scripting surface