Just so everyone doesn't think this is "done" per se (parts of it are),
work is still on-going upstream in https://secure.phabricator.com/T4788
See, for instance, the work on creating the task dependency tree. It's
already gone through a few iterations today and will probably change
more.
Greg
(Mostly) Max: Jira only allowed 3 levels of tasks, which was frustrating.
If phab adds "types" of subtasks, I hope it doesn't fall into that same
trap.
(Mostly) Joel: Yes, I would definitely favor distinguishing between
blocking tasks and subtasks. Trying to cover both cases with one set of
terms
aren't those both parent/child relationships? What's the difference?
*-- Joel Aufrecht*
Team Practices Group
Wikimedia Foundation
On Fri, Jul 1, 2016 at 10:39 AM, Max Binder wrote:
> I know my teams would love to distinguish between subtasks (of tasks with
> story points) and children (of ep
I know my teams would love to distinguish between subtasks (of tasks with
story points) and children (of epics). I don't think that is possible right
now, so they often use the title prefix "[Subtask]".
On Fri, Jul 1, 2016 at 10:25 AM, Joel Aufrecht
wrote:
> Should we make (or find and join) a r
Should we make (or find and join) a request that they provide a way to
differentiate between the two cases? Possible uses:
different display in the UI
use in data analysis, e.g., summing up tasks by summing up their subtasks
(and not dependencies)
*-- Joel Aufrecht*
Team Practices Group
Wikime
This week, phabricator changed the terminology it uses for managing
dependencies between tasks. What has been called "Blocking"/"Blocked by" is
now called "Parent"/"Subtask". Ignoring phab terminology for a minute, here
are the two basic cases these terms are covering:
1. *Sequential dependencies.
