Page MenuHomePhabricator

Multiple workboards per project
Closed, DeclinedPublic


Upstream task:

As reported by @MarkTraceur:

Having one workboard per project is a start, but we have projects where multiple different workboards would be very useful.



Event Timeline

flimport raised the priority of this task from to Lowest.Sep 12 2014, 1:32 AM
flimport set Reference to fl240.

qgil wrote on 2014-04-28 14:54:06 (UTC)

This task has been prioritized as Low upstream. Setting priority here accordingly.

Our request upstream is still vague when it comes to define use cases. I believe that we can get better progress if we help defining how this feature fits in Phabricator' s plans.

swalling wrote on 2014-04-28 20:59:15 (UTC)

I am not sure we should bother upstreaming this. This problem can be solved two ways:

  1. Create a separate project
  2. Create a column in a project's workboard. (Column name is displayed along with the project status for each task.)

This strategy is essentially how we solve the same problem in Trello, using separate boards, columns, and labels.

qgil wrote on 2014-04-28 21:48:34 (UTC)

There is a potential inertia in this direction upstream, and we can simply piggyback on it.

aklapper wrote on 2014-07-06 20:36:00 (UTC)

WONTFIXed in upstream, plan is to try subprojects first: "will make an attack on sprints/milestones/versions" (which might help for T166).

qgil wrote on 2014-07-10 13:00:38 (UTC)

The original request says "we have projects where multiple different workboards would be very useful."

Which different workboards, and useful what for? Without having more detail, I would consider resolving as Wontfix here as well.

marktraceur wrote on 2014-07-14 15:35:44 (UTC)

Yeah, I think that's probably fine - we have multiple workboards for different sprints and the like, but we could probably just use a catch-all "unplanned" status for the same thing.

aklapper wrote on 2014-08-28 21:16:05 (UTC)

Closing as DECLINED as per last two comments.