Assignee Mode

​

Overview

​

Widget Parameters

​

Configuration Properties

​

Required Data Structure

• At least one Polarion role must be assigned to the relevant users (e.g. project_user).
• Work items must have an assignee field set to a user who holds the configured role.
• When using Team Assignments for Plan-range filtering (activeTeamAssignmentsInPlanRangeOnly=true), the project must have configured Teams and Team Assignments.

​

How Swimlane Population Works

1. The board reads all users who hold the role specified in userRole.
2. One swimlane row is created per matching user.
3. Each work item is placed in the swimlane whose user matches the item’s assignee.
4. Items with an assignee not present in the user list (or with no assignee) go to Not Assigned/Other.

​

Teams Service Integration

• Team membership data is sourced from the Teams Service rather than solely from role membership.
• Per-user capacity values come from the Teams Service, enabling the capacity bar to reflect actual user capacity.
• The selectedTeam widget parameter filters swimlanes to members of a specific team.

​

Drag-and-Drop Behavior

• Dragging a card from the Unplanned sidebar to a swimlane row assigns the work item to that row’s user and plans it into the target column (Plan).
• Dropping a card on a different swimlane row reassigns the work item’s assignee to that row’s user.
• Holding Alt while dragging creates a duplicate assignment: the item is added to the target user in addition to the original assignee (comma-separated assignee list). Duplicating to the Not Assigned/Other swimlane is not supported.
• Cards with status Verified cannot be moved or unplanned.

​

Capacity Bar

• Column-level capacity bars aggregate effort for all items in that Plan column.
• When userCapacityLoad=true and the Teams Service is active, capacity bars reflect per-user available capacity sourced from Team Assignments.
• Hovering over a capacity bar shows a detailed tooltip (requires capacity configuration via widget parameters).

​

Filtering Plan-Range Active Users

nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true

• Project has configured Teams and Team Assignments.
• Nextedy PLANNINGBOARD is configured with user-based swimlanes derived from Team Assignments.
• Property set under Polarion Administration → Configuration Properties.

​

Configuration Example

assignmentMode=ASSIGNEE
userRole=project_user
showEmptySwimlanes=false
collapsibleSwimlanes=true
swimlaneSort=alphabetical

nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true

​

Limitations

• No multi-assignee capacity distribution. When a work item has multiple assignees, its effort is not distributed across multiple swimlanes. The capacity calculation does not split effort proportionally between co-assignees.
• Swimlane sort order is coupled to item sort order. Changing the swimlane sort may affect the item sort order within cells.
• Assignee mode sources users from the current project’s role membership. Cross-project user lists require the Project Mode or a SAFe assignment type.
• Team Assignment-based Plan-range filtering (activeTeamAssignmentsInPlanRangeOnly) requires version 25.12.0 or later.

​

Related Pages

• Assignment Modes — overview of all available swimlane assignment types
• Swimlanes (Rows) Parameters — full widget parameter reference for swimlane configuration
• Capacity Parameters — configure capacity bars and effort tracking
• Teams Service Properties — Teams Service integration properties
• Parent Item Mode — swimlanes grouped by parent work item instead of assignee
• Enumeration Field Mode — swimlanes grouped by a custom enumeration field
• Project Mode — swimlanes grouped by sub-project