Open oparoz opened 7 years ago
This is very useful for properties that apply to cards at any state in the state (stack) in the board
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.
@xenithorb Good idea to use labels for that.
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.
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.
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
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.
Very interested in swimlanes to get my priorities right in my boards.
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.
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.
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
Hey there,
I'd just like to let you know that due to the ongoing issue with Bountysource we're discussing ways to move to a different platform. As it looks right now, Bountysource might claim some of the money that was contributed by the community. We will try our best to prevent that. Historically we – the Nextcloud GmbH employees – simply put the claimed bounties back to other tickets until one was solved by a community member. So the money was always from the community and for the community. We'll therefore move to a better platform and currently don't post any new bounties until this situation is resolved. The current goal is to move/donate the money to Nextcloud include but details will follow in the forum post.
Hope this makes sense. If you have any questions please ask them on the forum. This comment will be copy-pasted to all open issues with bounties.
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:
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.