|Resolved||Qgil||T553 Engineering Community team goals for October 2014|
|Resolved||Qgil||T174 Launch Wikimedia Phabricator Day 1|
|Resolved||Qgil||T175 Nominate a team in charge of deploying and maintaining Wikimedia Phabricator code|
|Resolved||• RobLa-WMF||T17 Allocate resources for the migration and maintenance|
|Resolved||Qgil||T19 Define which features existing in our current tools are really missing in Phabricator|
|Resolved||Awjrichards||T20 Identify features Mingle users would miss in Phabricator|
|Declined||Aklapper||T149 Multiple workboards per project|
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:
- Create a separate project
- 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-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.