Add Feature: Swimlanes (rows) #955
Comments
|
Swimlanes are definitely neeed when you want to keep the planing synchronized for multiple teams or projects. |
|
I am interested to know why this proposal has been downvoted. What are some of the down-sides to allowing boards to have swimlanes? |
|
Please ignore all trolls, spammers, downvotes etc in our issues, and discussion about those. All feature requests are considered good and can be implemented by those that wish to do so. |
|
There are some interesting reads on the web as to why horizontal rows (swimlanes) can make sense: |
|
Someone could look how swimlanes is implemented at Kanboard to get some ideas or use same libraries. Both Wekan and Kanboard use MIT license. |
|
Any update on this? |
|
There is no bounties for this feature. More info about bounties here. At old roadmap and new roadmap lists planned and in progress it seems that nobody is working on this feature. This does not seem to be so important to have in near future. |
|
Hello, I have a basic draft of swimlanes for Wekan. Could someone try it out? What is implemented:
What is missing:
Note: All lists are shared across swimlanes. They belong to the board. So if a new list is created, it appears automatically on all swimlanes. Screenshot |
|
I did try that code. Suggestions:
That offtopic vertical layout is mentioned at separate themes issue and looks similar like this Jira screenshot middle column. Vertical layout can be looked at later. Comments, anybody? |
|
Reminder to myself:
|
|
Optional, maybe later additions. These partially are related to filtering. Ability to hide:
These would need some logical UI design. |
|
Today's release v0.65 includes Swimlanes part 1, please test Docker image at Quay.io: |
|
thx for this feature, i don't know how to delete a Swimlanes when i create 2 instead of 1 ? |
|
Hello @scoubidoo, I didn't get much free time to continue this development but it is in my TODO list. What is missing:
For the moment there basic functionality, I hope I have more time this week to continue. |
|
@andresmanelli ok no pb, i give you my feedback about this new feature |
|
Thanks.... I was also waiting for this. An ability to add and hide swim lanes is great if you can add. |
|
Hello again, @naveengh I just pushed a couple of commits that adds name edition and archive capability. Tests are welcome! @xe7 Could you or someone check if including commiit andresmanelli@42bc905 everything works fine? It works for me, but some people had issues, maybe because of cherry picking. Anyway, I'll try to add the sort capabiliity in a couple of days. |
|
Hi Everybody Each Project (or several similar Projects) have their own board. They plan development tasks with a lengt of 1-4 weeks. Each development task creates a swimline on the board with subtaks (should be around one day of work). The subtasks are then moved from "backlog" to "in progress" to "in review" and finally to "done". What we need now is the possibility to add some Attibutes to the Swimline. At least the following attributes are needed:
The best would be to add the possibility to define custom optional attributes for the swimlines. This would fullfill everyones requirements by configuration. |
|
BTW, @andresmanelli is doing excellent work with adding swimlanes, adding features, fixing bugs etc. I really recommend all users of swimlanes feature to add to bounty at https://www.bountysource.com/issues/43611228-add-feature-swimlanes-rows because there is none yet, and feature request list just keeps growing. More info about bounties at https://wekan.team . Wekan does not have any separate development and stable releases. There is only newest release, which currently is v0.70. We rely on Wekan users to add GitHub issues about bugs and feature requests. I don't know what you mean by attributes to Swimline. Wekan cards already have:
Wekan will sometime also have
So I don't know are you asking something that does not exist yet. Please add more details, screenshot mockups etc about what you would like to have. |
|
Thank you. I’m looking forward to test that feature once I get Wekan installed. Thanks for working on it and I will get back with testing results. @xet7 , I hope you have this feature on latest build. Thank you |
|
Yes, swimlanes is included in latest Wekan release. |
|
BTW you all do a great job here. There is so much flow in this project. I'm still impressed ... Back to my idea to have attributes for the swimline. I assume something similar to this: The first line is the so called identifier for the swimline. This means in our case a development task in a life cycle management tool. I have now decided to install wekan in the latest version in our environment and will use it as shown in the print screen above. What i mean is to add the attributes in the card in line "title" directly to the swimline. @andresmanelli |
|
Hello, I just wanted to say that I've my hands full and don't have any time these days to commit any changes. I try to add features and bug fixes as soon as I can. I see people are asking because things can be broken (#1492). Sorry about that, doing my best ! |
|
Thanks for update! I added it to Roadmap https://github.com/wekan/wekan/projects/2 Please do what is most important to you, there are other contributors that can look at those issues. Do not take any pressure about Wekan contributions, afaik you did not have any bounties yet, so we are just grateful what you did already. There is no requirement to spend additional time. |
|
Hello @xet7 @naveengh , commit andresmanelli@37c9462 adds reordering capability to swimlanes. @xet7 could you include this one and the one mentioned in #1487 ? |
|
@xet7 commit andresmanelli@8d2839f fix lists reorder in lists view. I don't remember any more where this was discussed. |
|
Hello, I just added two commits:
@xet7 could you try those? |
|
Maybe #1521 is related to these commits? |
|
These fixes are a great improvement but don't fully fix the alignment problems I put in #1497. I think that the swimlanes header needs to be set to a fixed width in wekan/client/components/swimlanes/swimlanes.styl, e.g. line 42 change "min-width: 30px;" to "width: 40px". 40 is a minimum, 50 or 60 might be better. Ideal would be to make it editable via the swim lane header menu but that's beyond me. to make the dividers more visible I've also done the following, but that's a personal taste issue I think. client/components/swimlanes/swimlanes.styl |
|
@johnleeming I tried your changes to *.styl files. I personally think 30% is a good compromise as 40% seems a little too dark. Can you try this? : diff --git a/client/components/lists/list.styl b/client/components/lists/list.styl
index fa32ff6..746e59b 100644
--- a/client/components/lists/list.styl
+++ b/client/components/lists/list.styl
@@ -9,8 +9,8 @@
// Even if this background color is the same as the body we can't leave it
// transparent, because that won't work during a list drag.
background: darken(white, 13%)
- border-left: 1px solid darken(white, 20%)
- border-bottom: 1px solid #CCC
+ border-left: 1px solid darken(white, 30%)
+ border-bottom: 1px solid darken(white, 30%)
padding: 0
float: left
diff --git a/client/components/swimlanes/swimlanes.styl b/client/components/swimlanes/swimlanes.styl
index 29054d3..78f2441 100644
--- a/client/components/swimlanes/swimlanes.styl
+++ b/client/components/swimlanes/swimlanes.styl
@@ -29,7 +29,7 @@
flex-direction: row;
flex: 0 0 50px;
padding-bottom: 30px;
- border-bottom: 1px solid #CCC
+ border-bottom: 1px solid darken(white, 30%)
.swimlane-header
writing-mode: vertical-rl;And about the header width, I didn't understand why to increase the width? Do you see the headers unaligned? |
|
I'm happy with the 30%. |
|
@johnleeming Isn't this related to #1526? |
|
could be - I'm using Vivaldi browser which is based on the Chromium engine |
|
Swimlanes is already in Wekan. |
|
I'm new to Wekan so please excuse me if this is basic or if this has been discussed somewhere else. In all screenshots I have seen so far, swimlane titles are always shown as row headers. In my case, they are located on top of all the lists (see screenshot). I am not admin on the server so maybe this is a setting I cannot change myself, but if it is, I cannot find how to change it. Additionally, I haven't found an extensive documentation about Wekan, and in particular, info about swimlanes is difficult to find. Are you considering adding this? |
|
Swimlanes was changed from vertical to horizontal at #1688 . It can not be changed to vertical. There already is Swimlanes documentation at wiki https://github.com/wekan/wekan/wiki right menu Features topic, direct link: |
|
There will be later Collapse Swimlane feature (maybe also Collapse List) #2107 |
|
@xet7 Thanks a lot for the links! I indeed overlooked it under "Features", my bad... The collapse feature would indeed be a very good compromise (or the best of both worlds!) |
|
Yes, that Collapse feature has already been paid and is at Roadmap so it will be in Wekan sometime this year I think. |
Context
A common practice in Agile/Lean development is to group tasks by User Story. To facilitate the grouping, some Kanban tools support both rows and columns. The columns are commonly used to track task status/progress while rows provide a secondary grouping, such as:
Feature request
Allow Wekan boards to support multiple rows.
Example media
Additional examples
The text was updated successfully, but these errors were encountered: