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

# Filter Swimlanes by Team

> Show only the users who have active Team Assignments within the date range of the Plans currently displayed on the board.

When your board uses user-based swimlanes derived from Team Assignments, Nextedy PLANNINGBOARD can automatically hide team members who have no capacity assigned in the current Plan range. This keeps the board focused on people who are actually available for the plans you are scheduling, and moves any items assigned to hidden users to the **Not Assigned/Other** swimlane.

<Note title="Version requirement">
  This feature requires Planningboard **25.12.0** or later. An earlier property (`nextedy.planningboard.activeTeamAssignmentsOnly=true`) introduced in 25.3.0 is deprecated as of 25.12.0 — migrate to the new property described below.
</Note>

***

## Prerequisites

Before enabling this filter, confirm that your board meets both of the following requirements:

* The Polarion project has **Teams and Team Assignments** configured (users are assigned to teams with specific date ranges).
* The Planningboard widget uses **Users (Assignee)** as the swimlane assignment type, with swimlane users derived from Team Assignments.

If your swimlanes are populated from a user role (not from Team Assignments), this filter has no effect.

***

## Steps

### 1. Open Polarion Administration Configuration Properties

In Polarion, navigate to **Administration > Configuration Properties** for the project (or at the global level if you want this behavior across all boards in the instance).

### 2. Add the property

Add the following line to Configuration Properties:

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

Save the configuration.

<Tip title="Property not taking effect?">
  If the board does not reflect the change after saving, make a trivial edit to any other property in Configuration Properties and save again. This forces Planningboard to reload the configuration.
</Tip>

### 3. Reload the board

Refresh the Planningboard page. Users with no Team Assignment overlapping the date range of the currently displayed Plans will no longer appear as separate swimlane rows. Any work items previously assigned to those users are now grouped under the **Not Assigned/Other** swimlane row.

***

## How it works

<Frame>
  <img src="https://mintcdn.com/none-17b4493f/zUlmOSLBIQ0HyaAX/planningboard/diagrams/guides/swimlanes/filtering-by-team/diagram-1.svg?fit=max&auto=format&n=zUlmOSLBIQ0HyaAX&q=85&s=fa1869eab91f19744086ddd0be543a9d" alt="Flowchart showing how the activeTeamAssignmentsInPlanRangeOnly property decides whether swimlane rows are filtered to users with an overlapping Team Assignment or show all team members, with non-overlapping users moved to Not Assigned/Other" width="780" height="480" data-path="planningboard/diagrams/guides/swimlanes/filtering-by-team/diagram-1.svg" />
</Frame>

The filter compares each user's Team Assignment date range against the date range spanned by the Plans currently shown on the board. Only users with at least one Team Assignment that overlaps this window remain as visible swimlane rows.

***

## Also filter the Plans shown (recommended)

Filtering swimlane rows by Team Assignment range is most effective when you also restrict the **Plans** (columns) shown on the board to the same team. Without this second step, the board may display iterations belonging to other teams alongside the filtered swimlanes, which can be confusing.

To filter iterations by team using a page parameter, pass a `team` page parameter in your Planningboard widget and configure a Plans query that references it. See [Dynamic Filtering with Page Parameters](/planningboard/guides/advanced/dynamic-filtering) for the full setup, and [Configure Plans (Columns)](/planningboard/guides/configuration/plans-configuration) for Plans query syntax.

<Warning title="Incomplete setup">
  A common support issue arises when only the swimlane filter is enabled but the Plans query is left unfiltered. The swimlane rows show only members of the selected team, but the columns still include iterations from other teams. Always coordinate both configurations for a clean team-scoped board.
</Warning>

***

## What happens to items assigned to hidden users

When a user is hidden because they have no Team Assignment in the current Plan range:

* Their swimlane row is **removed** from the board.
* Any work items assigned to them appear in the **Not Assigned/Other** row at the bottom of the board.
* This signals that those items are unlikely to be completed by that person within the shown Plans, and should be reassigned or rescheduled.

<Warning title="Multi-assignee limitation">
  Items with multiple assignees currently display under only **one** swimlane row, not all assigned users. If one of those assignees is hidden by this filter, the item's placement may not reflect the remaining active assignee. This is a known product limitation — an enhancement to display items under all assignees' swimlanes is tracked but not yet shipped.
</Warning>

***

## Reverting to the deprecated property

If you are on an older version of Planningboard (25.3.0–25.11.x) and cannot upgrade, the earlier property hides only users with Team Assignments entirely in the past, regardless of the shown Plan range:

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

This property is **deprecated as of 25.12.0**. Migrate to `nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true` when you upgrade.

***

## Verification

After saving and refreshing:

* The board should show **only** the swimlane rows for users whose Team Assignment date range overlaps the Plans currently displayed.
* Users outside that range should be absent from the row list.
* Any items that were assigned to now-hidden users should appear in the **Not Assigned/Other** swimlane at the bottom.

If a user you expect to see is missing, verify their Team Assignment dates in Polarion and confirm they overlap at least one of the displayed Plans.

***

## See also

* [User and Assignee Swimlanes](/planningboard/guides/swimlanes/user-swimlanes) — configure the swimlane assignment type that this filter applies to
* [Filter Swimlanes by Plan Range](/planningboard/guides/swimlanes/filtering-by-plan-range) — related Plan-range filtering approach
* [Configure Swimlanes (Rows)](/planningboard/guides/configuration/swimlanes-configuration) — full swimlane widget parameter reference
* [Dynamic Filtering with Page Parameters](/planningboard/guides/advanced/dynamic-filtering) — filter both swimlanes and Plans by team using page parameters
* [Set Up Teams Service](/planningboard/guides/capacity/teams-service-setup) — prerequisite: configuring Teams and Team Assignments in Polarion

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

  * Filter user swimlanes by Plan range
  * Swimlane Assignment Types
  * Sorting of Swimlanes (Parent Item Assignment Type)

  **Support Tickets**

  * [#5760](https://support.nextedy.com/helpdesk/tickets/5760)
  * [#6681](https://support.nextedy.com/helpdesk/tickets/6681)
  * [#5922](https://support.nextedy.com/helpdesk/tickets/5922)

  **Source Code**

  * `filterMultiSwimlaneRows.cy.ts`
  * `PlanningBoardWidgetRenderer.java`
  * `licenseReadonly.cy.ts`
  * `AssignmentMode.java`
  * `PlanningBoardWidget.java`
</Accordion>