Page MenuHomePhabricator

2D Kanban
Closed, WontfixPublic

Description

For complex projects with many tasks would be nice to set tasks not only in different columns but also different rows.
An interesting use case can be to divide tasks into sprints (milestones) keeping also them grouped into streams, as in the following mockup:

.           +--------------+-------------+--------------+-------------+ 
.           | Future       | Release 1   | Beta         | Alpha       | 
.           | No Milestone | Milestone 3 | Milestone 2  | Milestone 1 | 
+-----------+--------------+-------------+--------------+-------------+ 
| Stream 1  | ...          | ...         | ...          | ...         | 
|           |              |             |              |             | 
+-----------+--------------+-------------+--------------+-------------+ 
| Stream 2  | ...          | ...         | ...          | ...         | 
|           |              |             |              |             | 
+-----------+--------------+-------------+--------------+-------------+ 
| ...       | ...          | ...         | ...          | ...         | 
|           |              |             |              |             | 
+-----------+--------------+-------------+--------------+-------------+

Some other considerations around internet (e.g. http://www.targetprocess.com/blog/2013/10/kanban-as-multiban.html)

Related Objects

Event Timeline

stevex raised the priority of this task from to Needs Triage.
stevex updated the task description. (Show Details)
stevex added projects: Projects, Maniphest.
stevex added a subscriber: stevex.
stevex updated the task description. (Show Details)
stevex updated the task description. (Show Details)

We expect sprints and milestones to come from Subprojects. So if that is your main problem, we'll just merge this task there. See T3670.

The point is to give a more powerful visualization to Phabricator Kanban.

This will help to better manage boards with many cards (with possibly filtering row-columns) but more to have even different viewpoints on the same task.

If you follow link provided you can find more examples and arguments for the purpose. Around the same link there are even more pages as:

We don't build features / solutions for the sake of building them, we need feature requests to state the problem they have with using Phabricator and only the problem. We may choose a different solution to solve your problem, one that solves many problems other real Phabricator users are encountering. If you can't state a problem you are having, it's not clear to me what we're building and why.

Filtering workboards is achieved via the filters at the top of the board. Sprints and Milestones will be better achieved with subproject support. The main issue is any problem you are currently having with workboards is likely already filed and planned under other tasks, so this task as currently stated, is not something we'd pursue.

This feature will for example solve the problem of visualizing all-together the tasks coming from different subprojects, without having to visualize the sub-tasks in each sub-project or alternatively having to have all of them mixed up in one (single dimension) Kanban.

Having them visualized in this way you have also the possibility with drag-and-drop of changing not one (as now) but two different "variables" in one time.

chad claimed this task.

We don't plan to pursue this in the upstream

Missed in the first instance this nice video: http://www.targetprocess.com/kanban/

(it is not about solving problems, it is also about enabling possibilities: http://www.targetprocess.com/solutions/scrum-for-a-company/, by processes and roles)