Filter Swimlanes by Plan Range - Nextedy Documentation

This guide applies when you are using user-based swimlanes derived from Team Assignments and want the board to automatically suppress rows for members whose assignments fall entirely outside the shown Plans.

Prerequisites

Before you begin, confirm that your board meets the following requirements:

The Nextedy PLANNINGBOARD is configured with Teams Service enabled (useTeamsService = true).
Team Assignments are set up for the project (members have assignments with start and end dates).
Swimlanes use the Users (Assignee) assignment type, with rows derived from Team Assignments.
You are running Planningboard version 25.12.0 or later.

An earlier property, nextedy.planningboard.activeTeamAssignmentsOnly=true, was introduced in version 25.3.0 and deprecated in version 25.12.0. That version filtered only past assignments, without regard to the scope of the shown Plans. Do not use it for new setups — use activeTeamAssignmentsInPlanRangeOnly instead (documented below).

Planningboard showing swimlane rows for Mark Test, John Requirement, and Not Assigned / Other before plan-range filtering is enabled

How it works

Plan range window covering Sprint 10 through Sprint 12, and a Team Assignment overlap check showing Alice and Bob overlapping the range (SHOW) while Mark's assignment falls outside it (HIDE) and moves to Not Assigned / Other

When activeTeamAssignmentsInPlanRangeOnly=true is set, Planningboard calculates the combined date span of all Plans visible on the board and checks each team member’s assignments. Members whose assignments have no overlap with that span are hidden. Any work items already assigned to a hidden member are moved automatically to the Not Assigned / Other swimlane.

Steps

1. Open Polarion Administration Configuration Properties

In Polarion, navigate to: Administration > Configuration Properties

2. Add the property

Add the following property to your configuration:

nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true

3. Save and reload

Save the configuration. Planningboard will apply the filter on the next board load — no server restart is required.

If the board does not reflect the change immediately, make a trivial edit in Configuration Properties (add a space, then remove it) and save again. This forces the configuration cache to refresh.

4. Verify the result

Reload the Planningboard. Users who have no Team Assignments overlapping the date range of the currently shown Plans should no longer appear as swimlane rows. Any cards that were in their rows will have moved to the Not Assigned / Other swimlane.

Configuration example

A typical setup combining Teams Service with plan-range filtering:

# Enable Teams Service integration
nextedy.planningboard.useTeamsService=true

# Show only members with assignments in the displayed Plan range
nextedy.planningboard.activeTeamAssignmentsInPlanRangeOnly=true

Widget parameters (set in the Widget Parameters panel of your board):

Widget parameter	Value
Assignment Type	Users (Assignee)
Use Teams Service	enabled

Worked example

Scenario: Team Alpha is planning for three sprints (Sprint 10–12, covering January to mid-February). The board shows swimlanes for all team members. Mark Test left the team in December and has no assignment for this window. Before enabling the property: The board shows a swimlane for Mark Test even though he has no capacity in the planning window. Tasks that slip into his row are unlikely to be completed.

Board showing Mark Test's swimlane before filtering is enabled

After enabling activeTeamAssignmentsInPlanRangeOnly=true: Mark Test’s swimlane disappears. Any tasks that were assigned to him move to Not Assigned / Other, making the capacity gap visible and prompting reassignment.

Board after filtering — Mark Test's row is hidden and his items moved to Not Assigned / Other

This ensures that capacity shown on the board reflects only members who can realistically take on work within the planning window.

Limitations

This feature requires Planningboard 25.12.0 or later. Earlier versions do not support plan-range-aware filtering.
The filter is applied at board load time — it reflects the Plans currently shown. If you scroll the board to display a different Plan range, the visible swimlane rows update accordingly on the next load.
Items assigned to a hidden member are surfaced in Not Assigned / Other, not silently dropped. Review that swimlane after enabling the filter to reassign any affected cards.
This behavior applies only to swimlanes derived from Team Assignments. User swimlanes based on project role membership (not Teams Service) are not affected.

Verification

After completing the steps above, reload the Planningboard. You should see:

Swimlane rows only for team members whose Team Assignments overlap the date range of the Plans shown.
A Not Assigned / Other swimlane at the bottom containing any cards previously belonging to hidden members.
No swimlane row for members whose assignments fall entirely before or after the current Plan window.

​Prerequisites

​How it works

​Steps

​1. Open Polarion Administration Configuration Properties

​2. Add the property

​3. Save and reload

​4. Verify the result

​Configuration example

​Worked example

​Limitations

​Verification

​See also

Prerequisites

How it works

Steps

1. Open Polarion Administration Configuration Properties

2. Add the property

3. Save and reload

4. Verify the result

Configuration example

Worked example

Limitations

Verification

See also