Page MenuHomePhabricator

Ability to designate sub-workboards in Phabricator
Closed, DeclinedPublic

Description

Upstream task about sub-projects: https://secure.phabricator.com/T3670

As someone who monitors a workboard for a large team that works on many projects, I would like to be able to easily narrow my focus to the activity of a particular project. Even though I can filter the project, I would like to have some assurance that the workboard for the team is in sync with the workboard for the project, if it exists. For example, as of this writing, the workboard for the "MediaWiki Core Team" filtered to only show CirrusSearch tasks is out of sync with the CirrusSearch workboard.

One solution is to make it possible to designate a project's workboard as a sub-board of another board. So, in the case of CirrusSearch, it would be possible to designate that to be a sub-board of MediaWiki Core, so that the view in the board would be equivalent to if the MediaWiki Core board was filtered to only show CirrusSearch tasks. The tasks that only exist in CirrusSearch and not in the MediaWiki Core parent would ideally still show up on the CirrusSearch board (thus being different than a mere filtered view of the parent board), but wouldn't be expected to show up in the parent board.

Event Timeline

RobLa-WMF raised the priority of this task from to Needs Triage.
RobLa-WMF updated the task description. (Show Details)
RobLa-WMF added a project: Phabricator.
RobLa-WMF changed Security from none to None.
RobLa-WMF subscribed.
Qgil triaged this task as Lowest priority.Dec 11 2014, 8:18 AM
Qgil edited projects, added Phabricator (Upstream); removed Phabricator.

This is an interesting idea that would address the problems that we are hearing about having to keep several workboards in sync when oine task belongs to many.

It is a complex feature to implement, though (i.e. what happens whn your different subprojects are using different columns, and a task is moved to a column... that you don't have in your main board?). Probably most importantly, sub-workboards require sub-projects, and I don't expect upstream to pay much attention to this feature request before addressing the problem of subprojects: https://secure.phabricator.com/T3670

What I would like is to go to https://phabricator.wikimedia.org/project/ and clicking on Workboard(s) takes me to a list of workboards associated with the project.

We are currently considering mobile web working on 2 very separate features that would have completely different bug and product backlogs. Throw in different iteration boards.. then having just the one 'official' workboard is not good for us and if we had 2 projects I worry that my be confusing to people filing bugs.

We are currently considering mobile web working on 2 very separate features that would have completely different bug and product backlogs.

Sounds like to legit projects to me...

Throw in different iteration boards.

... having their own sprint projects each, if you want...

then having just the one 'official' workboard is not good for us and if we had 2 projects I worry that my be confusing to people filing bugs.

Naming the projects as Mobile-Web-Feature1 and Mobile-Web-Feature2 there shouldn't be any problem. Users will either notice that Feature1/2 is what they are looking for, otherwise they will go for the plain Web-Team-Backlog project (or even Mobile if they are totally unsure).

I still think that the principle of one workboard for one project is the right approach here. Projects are cheap. Subprojects are somewhere in Phabricator's roadmap: https://secure.phabricator.com/T3670

If we submit a request for sub-workboards, the most likely outcome will be to merge our request with https://secure.phabricator.com/T3670. I would either decline this task, or convert it in a request for subprojects.

Qgil claimed this task.

I would either decline this task, or convert it in a request for subprojects.

Subprojects is a feature that upstream has already in mind, so there is little point in mirroring it here. Declining.