> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Assignee Mode

> **Assignee mode** is a swimlane assignment type that groups work items into horizontal swimlanes by the user assigned to each item.

## Overview

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/zUlmOSLBIQ0HyaAX/planningboard/diagrams/reference/assignment-modes/assignee-mode/diagram-1.svg?fit=max&auto=format&n=zUlmOSLBIQ0HyaAX&q=85&s=c51a191623b33866872e08c14736951f" alt="Planningboard board view hierarchy: columns are Plans (Iterations, PIs, etc.) and rows are swimlanes, one per assignee — Alex Seller and Carl User as users with a matching role, plus a Not Assigned/Other catch-all row for items with no matching assignee" width="1050" height="310" data-path="planningboard/diagrams/reference/assignment-modes/assignee-mode/diagram-1.svg" />
</Frame>

When Assignee mode is active, the board shows one swimlane per user who holds the configured **User Role** in the current project. Work items are placed in the swimlane matching their assignee field. Items whose assignee does not match any displayed swimlane appear in a catch-all **Not Assigned/Other** row.

***

## Widget Parameters

Configure Assignee mode in the **Swimlanes (Rows)** section of the Widget Parameters panel. Set **Assignment Type** to `Users (Assignee)`.

| Parameter              | Type    | Default        | Description                                                                                                                                                   |
| ---------------------- | ------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `assignmentMode`       | string  | `ASSIGNEE`     | Activates Assignee mode. Set to `ASSIGNEE` (case-sensitive).                                                                                                  |
| `userRole`             | string  | —              | Polarion role ID whose members populate the swimlanes. Example: `project_user`. Only users holding this role in the current project appear as rows.           |
| `showEmptySwimlanes`   | boolean | `false`        | When `true`, displays swimlanes for all matching-role users even if they have no planned work items in the current view. When `false`, empty rows are hidden. |
| `swimlaneSort`         | string  | `alphabetical` | Sort order for swimlane rows. Value `alphabetical` orders users by display name. Other values depend on the application configuration.                        |
| `collapsibleSwimlanes` | boolean | `true`         | Allows users to collapse and expand individual swimlane rows. Useful when the board has many assignees.                                                       |
| `reportLink`           | string  | —              | Optional. URL or report identifier to attach a per-swimlane report link for deeper analysis.                                                                  |

<Note title="User Role is required">
  If `userRole` is not set, the board cannot determine which users to display as swimlane rows. Set it to a valid Polarion role ID — for example, `project_user` — to populate the board.
</Note>

***

## Configuration Properties

The following administration-level configuration properties affect Assignee mode behavior. Set these in **Polarion Administration → Configuration Properties**.

| Property                                                     | Type    | Default | Description                                                                                                                                                                                                                                                                                                   |
| ------------------------------------------------------------ | ------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly` | boolean | `false` | When `true`, user swimlanes derived from Team Assignments show only users whose Team Assignment overlaps the time range of the currently displayed Plans. Users with assignments entirely outside the shown Plans are hidden; their items move to **Not Assigned/Other**. Available from version **25.12.0**. |
| `nextedy.planningboard.activeTeamAssignmentsOnly`            | boolean | `false` | **Deprecated since 25.12.0.** Earlier variant that hid only past Team Assignments regardless of Plan scope. Use `activeTeamAssignmentsInPlanRangeOnly` instead.                                                                                                                                               |

<Warning title="Deprecated property">
  `nextedy.planningboard.activeTeamAssignmentsOnly` was introduced in version 25.3.0 and deprecated in version 25.12.0. Migrate to `nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true` for Plan-range-aware filtering.
</Warning>

***

## Required Data Structure

For Assignee mode to populate swimlanes correctly, the project must meet these requirements:

* 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

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/zUlmOSLBIQ0HyaAX/planningboard/diagrams/reference/assignment-modes/assignee-mode/diagram-2.svg?fit=max&auto=format&n=zUlmOSLBIQ0HyaAX&q=85&s=c8746f0ecde4aef8c59f52d81e34160a" alt="Assignee mode swimlane resolution: the project_user role members Alex Seller and Carl User define the board swimlane rows, while work items WI-1, WI-2, and WI-3 are routed into the matching swimlane, with the unmatched WI-3 (assignee Dana, no matching role) falling into Not Assigned/Other" width="940" height="460" data-path="planningboard/diagrams/reference/assignment-modes/assignee-mode/diagram-2.svg" />
</Frame>

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

When `useTeamsService=true` is set on the widget, Assignee mode integrates with the Polarion Teams Service:

* 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.

See [Swimlanes (Rows) Parameters](/planningboard/reference/widget-parameters/swimlanes-parameters) and [Teams Service Properties](/planningboard/reference/configuration-properties/teams-properties) for related configuration.

***

## 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

When `capacityLoad=true` is enabled, each swimlane displays a capacity bar showing planned effort against available capacity. In Assignee mode:

* 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).

See [Capacity Parameters](/planningboard/reference/widget-parameters/capacity-parameters) for the full set of capacity configuration options.

***

## Filtering Plan-Range Active Users

When your project uses Team Assignments and you want swimlanes to reflect only users active during the displayed Plans:

```properties theme={null}
nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true
```

**Effect:** users whose Team Assignments fall entirely outside the date range of the currently shown Plans are hidden from the board. Their work items are moved to **Not Assigned/Other**.

**Required setup:**

* 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.

<Tip title="Property not applying?">
  If the property does not take effect after saving, make any minor change in Configuration Properties and save again to force a refresh.
</Tip>

***

## Configuration Example

The following example configures a Planningboard widget with Assignee mode using the `project_user` role, with empty swimlanes hidden and collapsible rows enabled.

**Widget Parameters (Swimlanes section):**

```properties theme={null}
assignmentMode=ASSIGNEE
userRole=project_user
showEmptySwimlanes=false
collapsibleSwimlanes=true
swimlaneSort=alphabetical
```

**Configuration Properties (for Plan-range filtering, optional):**

```properties theme={null}
nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true
```

**Scenario:** A project has two users — Alex Seller and Carl User — both with the `project_user` role. The board displays one swimlane per user. A third user, Mark Test, has no Team Assignment within the shown Plans' time range; with `activeTeamAssignmentsInPlanRangeOnly=true` enabled, Mark Test's swimlane is hidden and any items assigned to him appear in **Not Assigned/Other**.

***

## 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](/planningboard/reference/assignment-modes/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](/planningboard/reference/assignment-modes/index) — overview of all available swimlane assignment types
* [Swimlanes (Rows) Parameters](/planningboard/reference/widget-parameters/swimlanes-parameters) — full widget parameter reference for swimlane configuration
* [Capacity Parameters](/planningboard/reference/widget-parameters/capacity-parameters) — configure capacity bars and effort tracking
* [Teams Service Properties](/planningboard/reference/configuration-properties/teams-properties) — Teams Service integration properties
* [Parent Item Mode](/planningboard/reference/assignment-modes/parent-mode) — swimlanes grouped by parent work item instead of assignee
* [Enumeration Field Mode](/planningboard/reference/assignment-modes/enum-mode) — swimlanes grouped by a custom enumeration field
* [Project Mode](/planningboard/reference/assignment-modes/project-mode) — swimlanes grouped by sub-project

<Accordion title="Sources">
  **KB Articles**

  * Swimlane Assignment Types
  * Filter user swimlanes by Plan range
  * Planningboard interface & basic interactions

  **Support Tickets**

  * [#5879](https://support.nextedy.com/helpdesk/tickets/5879)

  **Source Code**

  * `PlanningBoardWidgetRenderer.java`
  * `PlanningBoardDataService.java`
  * `PlansMode.java`
  * `PlanningBoardWidget.java`
  * `AssignmentMode.java`
</Accordion>