Skip to main content

​
Does Planningboard support multiple assignees on a single work item?

Polarion itself allows a work item to have multiple assignees, and Planningboard will display the item on the board. However, when swimlanes use the Users (Assignee) assignment type, a work item with multiple assignees currently appears under only one swimlane, not under every assigned user’s lane. This is a known product limitation.
Items with multiple assignees are not duplicated across all matching user swimlanes. Only one assignee’s lane will show the card. If your team relies on per-person capacity tracking, treat this as a planning constraint until the enhancement is shipped.

​
Which swimlane does a multi-assignee item appear in?

The item appears in the swimlane of one of its assignees. The exact assignee whose lane is used depends on how the data service resolves the assignment at render time; there is no user-configurable rule for choosing which assignee “wins.” To avoid ambiguity, Nextedy recommends assigning items to a single user when using user-based swimlanes.

​
Will multi-assignee items count toward capacity for all assigned users?

No. Because the card appears in only one swimlane, its effort is counted toward only that swimlane’s capacity bar. The other assigned users’ capacity bars are unaffected by the item. This means per-user capacity totals may be inaccurate when items carry multiple assignees.
For accurate per-user capacity tracking, ensure each planned work item has a single assignee. If shared ownership is required, consider using a team-level swimlane (Project or Enumeration Field assignment type) instead of Users (Assignee).

​
Is there a planned fix to show the card under all assignees’ swimlanes?

Yes. The behavior — showing a multi-assignee item under all of the assigned users’ swimlanes rather than just one — is a tracked enhancement. Until it ships, the workaround is to assign items to a single user per sprint, or to use an alternative swimlane assignment type that does not rely on individual user identity.

​
What swimlane assignment types are available if Users (Assignee) does not fit my workflow?

Planningboard offers several swimlane assignment types. The table below summarizes the options and how they handle multi-assignee scenarios:
Table of swimlane assignment types and how each handles multi-assignee work items: Users (Assignee) shows the card in only one swimlane (limitation), Enumeration Field places it by enum value, Parent Item places it under its parent, Project places it under the item's project, SAFe Team / SAFe ART Team places it by SAFe team field (contact support), and No Swimlanes shows all cards in a single flat view
For team-based planning without the single-assignee constraint, the Enumeration Field assignment type using a team custom field is a practical alternative. See Swimlanes FAQ for configuration details.

​
Can I use page parameters to filter swimlanes dynamically by team or user?

No. Planningboard swimlane configuration does not currently support Polarion page parameters (for example, $pageParameters.xxx) for dynamic filtering of swimlane rows. Swimlane configuration is static per widget instance. The supported workaround for multi-team deployments is to create a separate Planningboard page per team, each with its own hardcoded swimlane configuration.
Configure a dedicated Planningboard widget page for each team, with the swimlane User Role or Enumeration Field set to that team’s scope. This avoids the need for dynamic page parameters.

​
Does Planningboard support custom Team work item types for swimlane rows?

No. Planningboard swimlane row configuration requires Nextedy’s standard Team work item type with the expected custom fields. Custom Team work item types — where you define your own fields and structure — are not supported in Planningboard swimlane rows. If your organization uses a custom Team WI type, consider using Nextedy GANTT (which supports custom team types from version 25.5.0 onward) as your primary planning tool, and use Planningboard as a complementary view.

​
How do I configure the Users (Assignee) swimlane type correctly?

In the widget’s Swimlanes (Rows) section, set Assignment Type to Users (Assignee) and set User Role to the Polarion role that identifies your project team members — for example, project_user. Only users holding that role in the current project will appear as swimlane rows. Users without the role are excluded regardless of whether they are assigned to work items. 
Widget Parameters → Swimlanes (Rows)

  Assignment Type : Users (Assignee)
  User Role       : project_user          ← role defined in Administration > User Management > Roles
  Report Link     : (optional)
See Swimlanes FAQ for the full list of assignment types and their configuration fields.

​
Why does a user swimlane appear empty even though they have assigned items?

This usually means one of the following:
  1. User Role mismatch — the user does not hold the role specified in the User Role parameter. Check Administration > User Management > Roles to confirm membership.
  2. Work item not matching the board query — the item is excluded by the Query or Query Type parameters. Verify the query returns the item in question.
  3. Multi-assignee display limitation — the item’s card is being rendered in a different user’s swimlane. Confirm the item has exactly one assignee matching this user.
Open the item directly in Polarion and verify both its assignee field and its role membership. If the item is correctly assigned and the user holds the right role, refresh the board using the Refresh button to reload the current state from the server.

​
Where can I learn more about swimlane configuration?

KB Articles
  • Swimlane Assignment Types
  • Introduction to Planningboard
  • Planningboard Widget Parameters
Support TicketsSource Code
  • PlanningBoardWidget.java
  • PlanningBoardWidgetRenderer.java
  • PlanningBoardDataService.java
  • licenseReadonly.cy.ts
  • PlanningBoardWidgetDependenciesProcessor.java
Last modified on July 9, 2026