Skip to main content

​
Board loads indefinitely (infinite spinner)

If the board never finishes loading and the spinner keeps running, the most likely cause is a network or firewall issue blocking Planningboard’s requests, not a product defect. Steps to diagnose:
  1. Open your browser’s developer tools (F12) and switch to the Network tab.
  2. Reload the page containing the Planningboard widget.
  3. Look for requests with status ERR_BLOCKED, ERR_CONNECTION_REFUSED, net::ERR_FAILED, or that hang without a response.
  4. If blocked requests appear, escalate to your IT/network team — a corporate firewall or proxy is likely filtering the Polarion server’s internal API calls.
  5. If no blocked requests appear, check the Console tab for JavaScript errors (see Script Errors).
In evaluated or restricted environments, internal firewall rules can silently block the Polarion API endpoints that Planningboard uses to load plans and work items. The board renders its shell but waits indefinitely for data. This has been confirmed as the root cause in multiple support cases — the fix is on the network side, not the product configuration.
Some proxy configurations intercept browser requests differently per browser. If Chrome shows blocked requests but Microsoft Edge does not, switching to Edge may be a working interim workaround while network access is resolved.

​
Clicking a swimlane expands the wrong one

When you click to expand a swimlane, a different swimlane (often the last one in the list) expands instead. This is a known intermittent UI issue affecting Google Chrome. Microsoft Edge handles this correctly. Workaround:
  1. Switch to Microsoft Edge for Planningboard sessions that require frequent swimlane interaction.
  2. If you must use Chrome, try refreshing the board using the Refresh button before expanding swimlanes — this resets the board’s internal state.
  3. If the issue persists in Chrome, scroll the swimlane list so the target swimlane is fully visible before clicking.
Clicking a swimlane in Chrome intermittently expands a different swimlane (typically the last one). No fix has been shipped at time of writing. Use Microsoft Edge as the confirmed working browser for swimlane-heavy workflows.
See Swimlane Expansion Issues for additional context.

​
”Field is not enumeration” error on swimlane configuration

This error appears when configuring enumeration-based swimlanes and the selected field is not recognized as a valid enum type. Supported field types for ENUM assignment mode:
  • Fields of type IEnumType
  • List fields (IListType) where list items are of type IEnumType
Fields that are NOT supported as swimlane grouping fields:
  • status
  • resolution
  • type (work item type)
Steps to resolve:
  1. In the widget configuration, locate the Resource Field selector (visible when Assignment Mode is set to ENUM).
  2. Verify the selected field is a custom enumeration field — not status, resolution, or type.
  3. If using a project-specific enum field, confirm it is registered at the global field level in Polarion administration. Project-local fields may not resolve correctly.
  4. After correcting the field selection, save the widget configuration and rebuild the board configuration by reloading the page.
  5. If the error persists after a field change, clear the Polarion server cache (Administration > Maintenance > Clear Caches) and reload.
These built-in Polarion fields use a different internal type and cannot be used as swimlane grouping fields in ENUM assignment mode. Attempting to use them produces a field validation error. Use a custom enumeration field instead.
Enum fields defined only at the project level may fail to resolve in cross-project or multi-project board configurations. Register enum fields at the global administration level when you need them to work reliably across projects.

​
Multi-enum swimlane support

Grouping swimlanes by a multi-valued enumeration field (where a work item can belong to more than one enum value simultaneously) is not yet fully supported. The feature gap was acknowledged by the product team and is planned for release. Until it ships, work items that have multiple values in the swimlane grouping field may not appear in all expected swimlanes, or the configuration may produce a validation error. Current workaround:
  • Use a single-value enumeration field for swimlane grouping.
  • For resource capacity management across multiple teams or components, consider User and Assignee Swimlanes as an interim approach.
See Enumeration Field Swimlanes for supported configuration steps.

​
Plan creation and unplanned sidebar not visible

If the Create New Plan button or the Show Unplanned button is missing from the board toolbar, the most likely cause is that your Polarion user account does not have a Planningboard license assigned. Planningboard enforces license-based access control: Steps to resolve:
  1. Ask your Polarion administrator to check whether your account has a Planningboard license assigned (Administration > Nextedy PLANNINGBOARD > Licenses).
  2. If you are an administrator, see License Count and Warnings for license assignment steps.
  3. If you have a license but these controls are still hidden, reload the page using the browser refresh (not the board Refresh button) to pick up the updated license state from the server.
Unlicensed users can still view all board content — plan columns, swimlanes, cards, and capacity bars. Dragging a card appears to work but changes are not saved to the server. This is intentional: it allows stakeholders and reviewers to observe planning without needing a license.
See License Count and Warnings for more detail.

​
Drag and drop does not save changes

Cards appear to move when dragged but snap back to their original position after the drop, or the change is not visible after a page reload. Common causes and fixes:
  1. Unlicensed user — Drag and drop is blocked for users without a Planningboard license. The card animates but the assignment is not persisted. See the section above.
  2. Read-only mode active — If the board is configured in read-only mode, all editing operations including drag and drop are disabled. Check the widget configuration for a read-only parameter.
  3. Insufficient Polarion permissions — The user needs write permission on the work items being moved. Check Polarion role assignments for the affected project.
  4. Plan date range mismatch — Work items are assigned to plans based on start_date and end_date. If the target plan’s date range does not encompass the work item’s dates, the assignment may be rejected silently.
See Drag and Drop Issues for a complete diagnostic flow.

​
Capacity bar shows no data or incorrect values

The capacity bar appears empty or shows values that do not match expected effort. Steps to diagnose:
  1. Confirm that Capacity Load is enabled in the widget configuration (capacityLoad parameter).
  2. Verify that the work items on the board have remainingEstimate or initialEstimate values set. If neither field has data, the capacity bar will be empty.
  3. If using a custom capacity field (capacityField), confirm the field ID is spelled exactly as it appears in the Polarion field configuration — the parameter is case-sensitive.
Extra spaces around parameter values in the widget configuration can cause the parameter to be ignored silently. Verify there is no leading or trailing whitespace in capacityField, hoursPerDay, or related capacity parameters.
See Capacity Calculation Issues for a full walkthrough.

​
Diagnostic flow

Planningboard admin-mode error popup showing a script syntax error: 'Item Script: SyntaxError: :1:24 Expected ) but found {'
Decision tree for diagnosing a Planningboard that fails to load, covering blocked network requests, JavaScript console errors, swimlane click and validation issues, missing buttons, and drag-and-drop save failures

​
Verification

After applying a fix, use the board’s Refresh button to reload the current state from the server without a full page reload. You should now see the board load completely, swimlanes expand to the correct row, the expected toolbar buttons appear, and card moves persist after a page reload.
Planningboard user-facing error popup showing 'There are issues with the data or configuration of this Planningboard. Please contact your project administrator to investigate and resolve the problem.'

​
See also

KB Articles
  • Troubleshooting Script Errors in Planningboard
Support TicketsSource Code
  • PlanningBoardWidgetDependenciesProcessor.java
  • PlanningBoardWidgetRenderer.java
  • PlanningBoardDataService.java
  • licenseReadonly.cy.ts
  • PlanningBoardWidget.java
Last modified on July 9, 2026