Repository navigation
Swimlanes support #32
Description
Would be nice to be able to split tasks in swimlanes.
A swimlane is a horizontal categorisation of cards in the active Kanban board on a board.
There is a $15 open bounty on this issue. Add to the bounty at Bountysource.
Reacted by Julius Knorr, Laurens de Groot, Michael Goodwin, Ben Schumacher, blubdibub, Stefan Haller, Vegar, vincowl, František Lachman, sh2515 and 36 more
Activity
xenithorb commentedon Apr 27, 2017
This is very useful for properties that apply to cards at any state in the state (stack) in the board
xenithorb commentedon Apr 27, 2017
I think swim lanes might be able to be implemented with the current label properties - that is, perhaps you could edit a label and mark it as "swim lane" and then it would show up as a horizontal part of the board UI. I don't know much about kanban, but from as far as I can tell labels server a similar function, just that they're not important enough to be actual horizontal lanes, so perhaps 'promoting' certain labels is a good way to implement swim lanes.
juliusknorr commentedon May 1, 2017
@xenithorb Good idea to use labels for that.
hftl-kalle commentedon Jun 9, 2017
I really don't like the horizontal scrolling. I think it would be more natural to sort all stacks into columns. The amount of columns would be determined by the width of the window. Googles Keep does a good job with this.
[-]Swimlanes support[/-][+]Swimlanes support [$15][/+]NebriBlackwing commentedon Aug 21, 2018
Just to clarify, swim lanes would essentially be containers for stacks? I could see that being very useful if we set up the swim lanes as rows that housed the stacks with show / hide functionality.
juliusknorr commentedon Aug 23, 2018
Somehow, a swimlane would more be a container for cards that are distributed across several stacks. I'd aim to something similar to the kanboard swimlane feature: https://docs.kanboard.org/en/latest/user_guide/swimlanes.html
stale commentedon Dec 24, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
2 remaining items
ml31415 commentedon Feb 9, 2019
Why not just create a new board with the same columns? Board_topic_lane1, Board_topic_lane2, done. There is no need to make simple things more complicated, than they need to be.
jirislav commentedon May 21, 2019
Because you can't group boards. Boards should not overlap with each other, that would be a mess.
Swimlanes are much more appropriate to group one kind of tasks on board. See an example on currently very popular issue tracker YouTrack: https://youtrack.jetbrains.com/agiles/153-308/155-3324
juliusknorr commentedon Jun 18, 2020
Nyco commentedon Jan 27, 2021
Swimlanes are:
Swimlanes are not labels: in Deck, the label feature is quite generic and fairly lonely, thus it is often overloaded (used as functional or technical classification, sometimes budget or event priority).
Swimlanes do not mean horizontal scrolling, it it the number of columns that detemines of your screen will need scrolling (and the columns reflect your process).
Products:
Nyco commentedon Feb 2, 2021
https://blog.taiga.io/taiga6-release.html#swimlanes-on-kanban
[-]Swimlanes support [$15][/-][+]Swimlanes support[/+]feat: add swimlane grouping by labels or assignees
feat: add swimlane grouping by labels or assignees
aktasfatih commentedon Sep 3, 2026
If anyone is still looking for swimlanes, feel free to check out my app Kanso https://github.com/aktasfatih/kanso. There is a Deck importer so you can import your boards right away.
You can find the swimlanes through Group By at the top right.
Thanks