Swimlanes

[preske87]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

• It's a feature request.
• I understood from another issue #32 that there was a discussion on swimlanes, which somehow ended.
• I would like to bring up the idea of swimlanes again, or however you want to call them

What are the use cases

• for a project team using a single kanban board, swimlines could be used to raise very important/critical issues to the top, i.e. having a swimlane "critical" at the top which holds e.g. tasks with close due date or high priority
• swimlanes allow to model a kanban-version of the Eisenhower-matrix by having a seggregation by urgency and importance
• swimlanes also allow to have "clusters" of task (typically by Epic). This then e.g. allows to have all tasks related for a given event in one cluster and not scattered all around the board

Describe the solution you'd like

• Swimlines, i.e. horizontal sections in the kanban board where tasks sharing the same attribute are located
• Allocation of tasks into a lane is distinct, i.e. one task is only allocated into one lane

Describe alternatives you've considered

• Taking the recommendation froms #32 different boards becomes messy

Additional context Add any other context or screenshots about the feature request here.

[calidancer]

Implementing swimlanes is the only way to combine the following two concepts:

1. Managing priority (allowed very well in the Eisenhower Matrix)
2. Tracking the progress of your tasks (allowed very well in Kanbanboards... specifically in this case in Nextcloud / Deck)

As you look at a typical Eisenhower matrix, tasks are divided into the following quadrants:

• P1: Urgent / Important (DO IT NOW)
• P2: Not Urgent / Important (SCHEDULE IT)
• P3: Urgent / Not Important (DELEGATE IT to a human or to an AI assistant)
• P4: Not Urgent / Not Important (DELETE IT)

Extensive research leads to the conclusion that utilizing Swimlanes in Kanbanboards (Nextcloud Deck in this case) is the most efficient method for task management, as it allows for accurate prioritization of tasks, avoiding disorganization.

Jira Atlassian already does this!

I have attached a screenshot of my Kanbanboard in Atlassian Jira for your reference:

Thanks for your attention.