Page MenuHomePhabricator

Mechanism for associating workboard columns with tags (projects)
Closed, ResolvedPublic

Description

(The solution to this problem will come with the implementation of "triggers" upstream -- https://secure.phabricator.com/T5474 )

In a recent IRC kvetch session regarding Phab workboards and how each new board has creates its own universe of task state entirely independent of other workboards or the task state, @GWicke said "I wished workboards were based on tags", by which he means "column==tag". I'm guessing it would be very close to impossible to convince upstream to change their entire model, but this strikes me as the obviously correct design the more I think about it.

That said, independent of complete revolution in how workboards work, it would be awfully useful for workboard actions to optionally trigger (via Herald?) some action which could cause projects (used as tags) to get added or removed from a project based on being added or removed from a given workboard column. For that matter, it would be even better if the opposite could also be true (adding/removing a project causes the item to move on the workboard). The one obvious complication here is that a task might need to be a member of multiple columns based on project membership, but that could also be an interesting feature. Alternatively, just making the leftmost project-associated column "win" might be a sufficient simplification.

Event Timeline

RobLa-WMF raised the priority of this task from to Needs Triage.
RobLa-WMF updated the task description. (Show Details)

Can you provide real examples of your need for this feature? I think I follow the concept, but it's still too abstract for me. Also, I'll have another mornin' cuppa tea. :)

Can you provide real examples of your need for this feature? I think I follow the concept, but it's still too abstract for me. Also, I'll have another mornin' cuppa tea. :)

For example, we could associate the VE Q3 blockers tag with the "VE Q3" column on the Parsoid workboard. Then, the addition of the VE Q3 blockers tag on a task already on the Parsoid workboard could automatically cause the task to move to the VE Q3 column.

Additionally, this would provide a means for the workboard state synchronization requested in T78225. Two workboards could have the same tags associated with the same columns, which would in turn cause the workboards to be synchronized.

Qgil set Security to None.

The solution to this problem will come with the implementation of "triggers" upstream -- see https://secure.phabricator.com/T5474#107048

mmodell claimed this task.
mmodell added a subscriber: mmodell.

This essentially is describing milestones.

Each milestone exists as a column on the parent-project's workboard. Moving a task into that column tags it with the milestone project. And conversely, tagging a task with a milestone moves it into that milestone's column.

This should probably be marked resolved since January of 2016.

Oh wow, this is changing my phabricator life. For future reference:

  • In the "subproject" tab in your main project, select "add milestone". I don't think it is possible to reorder milestones, so be strategic about the order you create them. They appear in creation order in the workboard.

And since Phabricator (2019-07-03) we have "Triggers": Every workboard column now offers a button in the column header. You can define which actions should be performed when a card (=task) is dragged into that workboard column.