Feature idea: Same cards, multiple column sets #211
Comments
|
I, for one, think this sounds really cool. |
|
Hi, This is an excellent idea, to abstract boards and cards, allowing multiple organizing schemas over the same cards. Libreboard is the best tool to create lists. Managing those "duplicated/meta cards" would affect the underlying boards, cleaning them of the "done" stuff. This would be another board collecting cards with specific attributes/tags/... However i'd like to still be able to user labels as it's relevant to have visual information on your cards better than the title. An API should be able to change the labels, so for example, travis could set green or red cards corresponding to builds. PS: i created an issue but closed it after reading yours :) |
|
The idea is very interesting/original, but i'm not sure about the use case, plus it may complexify the UI and the usability. For now I use Libreboard this way :
Furthermore, a task shouldn't be changing category, assignment, duration or priority that often, compared to the completion state IMO. |
|
@ultimatom - Sure, not everyone needs this feature, obviously. But some people have different needs. To address a few specific points:
|
|
The other interesting thing, is @kentonv's suggestion produces all the necessary info, potentially, to output things like Gantt charts. You could manage things simply and easily as one expects with this sort of app, and view the data in any number of traditional project planning methodologies. There's a lot of potential power to the concept of allowing the app to understand what it's doing (planning a project) rather than just being "lists of cards". |
|
I love the idea too, it is definitely something I'm missing in Trello right now! |
|
I agree, I extended MypersonalKanban (written in Angular) to do precisely this, and the result is fantastic, because as kentonv says, it allows you to visualise the cards and manipulate them from different perspectives. One moment you are planning what will go in the next few releases of product, and the next moment you are balancing the workload between team members. I can put up a demo or some screen shots if anyone is interested to see it |
|
@mikkelking Would you be interested in making it a Sandstorm.io app? :) We (sandstorm team) are happy to help; come talk to us on our discussion group or IRC (#sandstorm on Freenode). |
|
Have a look at how Asana can assign a single task to multiple projects and multiple sections. The idea and requirements are these:
The implementation that Asana team has provided is quite neat from the UX perspective and doesn't clutter the UI. In Asana terms, users can choose 0 or more projects/sections that a task can belong to. Inside those projects, the same task can be under completely different section in completely different order. For the marketing team your Feature X is the top priority, for security team this task is medium. Each team can rearrange the same task in their preferred way. Implementation wise it is relatively simple, too. In fact, the simpler you think, the easier will be to move on and make additional changes in the future. Here is how Asana team has implemented this feature. Each project (in Kanban terms this is a board) is a completely independent list. For now think of it as a linear array. Asana has visualized this list as a vertical list. Trelly and libreboard visualizes this same list horizontally. This doesn't matter. Now each such list (board) can contain 0 or more items (in Asana terms this is a section, in Libreboard terms this is a .... what? stage?) So, now we have an array of items each of which can be just a task/card or a card that can also contain a list of other items. This way, depending on the board, the same item can be placed at index [3, 2], meaning the 4th column/stage from the right and the second row from the top in this column. Since each item can be a card and also have a sub tasks/cards, this allow to create and link more granular tasks. These two features were one of the most frequently requested features in Asana when they had just opened. Another advantage of such implementation is the speed of retrieval. When the client loads, the server can serve the top X items all of which are already ordered and prioritized. If a user wants to see more items or scrolls left to see left-hand columns, they get loaded in one go as they are already sorted. I suppose this implementation would satisfy #207 as well. Another nice feature Asana provides is to duplicate a task and/or entire project with all their sections, tasks, and subtasks. This is what #134 wants. When implemented as a list of lists as described above, cloning is as simple as making a copy of the entire list. Order and priority will be preserved. The copy operation is essentially one database operation on a range. |
|
I'm commenting so I can subscribe to this issue alone, since I can't do that by subscribing (i.e. watching) ~ #283 |
|
I think this feature is great. |
I've been using Libreboard to organize the roadmap for Sandstorm.io, and I thought of what I think would be an incredibly powerful feature.
The basic problem right now is that there are several different ways in which I might want to organize my cards. For example:
Right now, I can only choose one of these to be my columns. Some of the others may be handled by labels or by assignments, but the UI for these is far less pleasant than dragging cards around. Setting a label requires 5 precision clicks and delay time while UI elements load. Dragging cards between columns is way more fun.
So what I want instead is to be able to define multiple column sets for the same set of cards. Then, instead of setting labels or assignments, I would switch to the column set I am thinking about at the moment and push cards around.
Moreover, when I'm looking at one column set, the cards should show internal labels indicating the card's position is column sets I'm not currently viewing. So, e.g., when I'm looking at "completion state" I can also see each card's "priority" shown inside the card. (It may be nice to be able to choose exactly which labels are shown in order to avoid clutter... not sure. It would also be nice if I could color-code the labels by assigning colors to the columns from which they are derived.)
With this feature implemented, the usual label and assignments features could potentially be removed, simplifying the code and further differentiating from Trello.
What do you think?
The text was updated successfully, but these errors were encountered: