A new terminology was recently introduced, where blocking tasks are now called "subtasks" and blocked tasks "parent tasks". The two terms are seemingly used as if they were one the opposite of the other, but they're not very intuitively such. It would be better to use terms which are clearly in opposition, so for instance parent task vs. child task or supertask vs. subtask, not a mix of the two. Or just blocked/blocking, of course.
Description
Description
Event Timeline
Comment Actions
IMO it's clearly intuitive, that subtask is blocker. In other words - without accomplishing the subtask (blocker), I can't obviously accomplish the current task (blocked), which is parent to that subtask.
Comment Actions
I don't think either that it is less intuitive or inconsistent (we also offer documentation on mw.org what these terms mean). Proposing to decline...
Comment Actions
". It would be better to use terms which are clearly in opposition, so for instance parent task vs. child task or supertask vs. subtask, not a mix of the two. Or just blocked/blocking, " is correct
Comment Actions
For me this is a huge blocker, which leads to lots of arguments and lost productivity. I would love to continue using this as I used "blockers", but when I add something as a subtask, it gets removed because "this task is not part of this other task", which technically is not, but it is a complete separate task blocking the other.
Either the terminology should change back to blocked by, blocking, or 2 kinds of relationships should be possible "X block Y" and "X is part of doing Y". A C-level has told me he will not use the relationship while it has the current terminology.
Comment Actions
If really wanted we can manually and locally change UI terms via translation.override in https://phabricator.wikimedia.org/diffusion/OPUP/browse/production/modules/phabricator/data/fixed_settings.yaml