add optional swimlanes / secondary grouping to Kanban board

Problem Statement

Currently, the Kanban board is organized by a single dimension: task status, represented by columns such as To Do, In Progress, and Done.

For larger teams or projects, it is often useful to see a second dimension at the same time — for example, who is responsible for each task.

At the moment, this requires filtering or mentally grouping tasks within each column, which becomes difficult when many tasks are visible on the board.

Proposed Solution

Add optional swimlanes to the Kanban board, similar to Jira.

The existing Kanban stages would remain as columns, while tasks could optionally be grouped into horizontal rows by another field.

For example:

	To Do	In Progress	Done
Alice	Tasks	Tasks	Tasks
Bob	Tasks	Tasks	Tasks
Unassigned	Tasks	Tasks	Tasks

A simple Group by selector could provide options such as:

• None
• Assignee
• Priority
• Label

Potentially, additional grouping options could be added later.

When None is selected, the board would behave exactly as it does today.

Alternative Solutions

A simpler alternative would be to support swimlanes only by Assignee initially.

Another option would be to rely entirely on filters, but filtering hides tasks rather than providing a second visual dimension, so it does not solve the same use case.

Relevant Context

The goal is not to replace the existing Kanban structure, but to add an optional second dimension.

For example, today the board answers:

What status is each task in?

With swimlanes it could additionally answer:

Who is responsible for the tasks in each status?

or:

What priority do the tasks in each status have?

This would be especially useful for team planning, workload visibility, and stand-ups.

Does this feature align with Kaneo's focus on simplicity?

Yes, if implemented as an optional board setting.

The default experience would remain unchanged, with no swimlanes enabled.

Users who need the additional structure could select a Group by option, while smaller projects could continue using the current simple Kanban layout.

This keeps the basic workflow simple while making the board more useful for larger teams and more complex projects.

---

Originally requested by @neonfit on 2026-09-17. Original GitHub request #1742.