I noticed that the Scrum-of-Scrums project workboard has columns for each of the #blocked-on-{team} tags.
The current workboard doesn't seem very useful or convenient since the columns won't automatically get updated with tasks tagged as blocked-on-{team}.
If we migrate the blocked-on-{team} tags to milestones under Scrum-of-Scrums then those workboard columns would be kept in sync with the state of the blocked-on-{team} milestones and we could easily see who's blocking who.
It says, "Objects may not be tagged with two different milestones of the same parent project. For example, a task may not be tagged with both Stonework → Iteration III and Stonework → Iteration V.
So the only potentially negative consequence is that you couldn't mark it as blocked on two teams at the same time (e.g. Blocked-On-Operations and Blocked-On-Security). This also just magically removes the old one ("When a milestone tag is added to an object which already has a tag from the same series of milestones, the old tag is removed.") rather than giving you an error.
I don't really use the Scrum-of-Scrums workboard, but maybe other people do and would find this a worthwhile tradeoff.
@Mattflaschen-WMF: That's a good point, I hadn't thought about blocked-on-multiple-teams...
So I guess more discussion is needed to decide if that is indeed a worthwhile tradeoff.
It's is not possible to have the task in more columns of the Scrum-of-Scrums workboard too. Which actually implies that the current related Scrum-of-Scrums workboard are pretty much worthless (and practically useless), especially considering their redundancy to various #blocked-on-{team} tags.
Suggesting to decline this, particularly also considering that the entire Scrum-of-Scrums board is not used so much.
We have not looked at the Scrum of Scrums workboard in the Scrum of Scrums meeting in over a year. Participants of the meeting suggested that we should remove the link to the board from our meeting notes and to archive the board to prevent confusion.
As we're not using either the Blocked-On-… or the workboard, why don't we scrap both?
@Jdforrester-WMF Please open a new task for that as it is not a part of the description of this one. Thank you.
No. This task is specifically about scrapping the "blocked on" projects. This is entirely germane.
This task was about moving the "blocked-on-*" tags to milestones, which is progressive action - changing of status of them from standalone to milestone, but not changing their existence.
It is not about their archiving (unless I misunderstood the meaning of scrapping tags == archiving tags) which is destructive action - making them nonexistent.
Please help keeping Phabricator well-arranged by following the habits and best practices about reporting tasks. Thank you.
It was. You did. But fine, I don't have an interest in prolonging your edit warring.
The context and wording of your post
implied archiving of those tags. If your intention was something different, then please elaborate it in less confusing wording, thannk you.
(And even if the intention was to "remove link to tags from meeting notes", it is still not a part of this task.)
And for the record: There have to be at least two sides to make a war, hence it is also your open/close warring, furthermore you were the one who started it apart from trying to discuss.