<div dir="ltr"><div>(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. <br><br></div>(Mostly) Joel: Yes, I would definitely favor distinguishing between blocking tasks and subtasks. Trying to cover both cases with one set of terms is very awkward, as one of my examples demonstrated: "implement X" certainly doesn't feel like a subtask of "document X", but that's how it will appear in phab right now.<br><br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><br>Kevin Smith<br>Agile Coach, Wikimedia Foundation<br></font></span><font><font><i><font color="#888888"><br></font></i></font></font></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Jul 1, 2016 at 11:27 AM, Max Binder <span dir="ltr"><<a href="mailto:mbinder@wikimedia.org" target="_blank">mbinder@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Technically, yes.<br><br></div>This distinguishes tasks that are subtasks of already-estimated (story pointed) tasks, so to avoid double estimation. JIRA, for example, has blocking tasks and subtasks, presumably for this purpose.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 1, 2016 at 10:40 AM, Joel Aufrecht <span dir="ltr"><<a href="mailto:jaufrecht@wikimedia.org" target="_blank">jaufrecht@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">aren't those both parent/child relationships? What's the difference?<br></div><div class="gmail_extra"><span><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font color="#888888"><div><b>-- <br>Joel Aufrecht<br></b></div><div>Team Practices Group<b><br></b></div><div>Wikimedia Foundation<br></div></font></div></div></div></div></div></div></div>
<br></span><div><div><div class="gmail_quote">On Fri, Jul 1, 2016 at 10:39 AM, Max Binder <span dir="ltr"><<a href="mailto:mbinder@wikimedia.org" target="_blank">mbinder@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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]".<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 1, 2016 at 10:25 AM, Joel Aufrecht <span dir="ltr"><<a href="mailto:jaufrecht@wikimedia.org" target="_blank">jaufrecht@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Should we make (or find and join) a request that they provide a way to differentiate between the two cases? Possible uses:<br><br></div>different display in the UI<br></div>use in data analysis, e.g., summing up tasks by summing up their subtasks (and not dependencies)<br></div><div class="gmail_extra"><br clear="all"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font color="#888888"><div><b>-- <br>Joel Aufrecht<br></b></div><div>Team Practices Group<b><br></b></div><div>Wikimedia Foundation<br></div></font></div></div></div></div></div></div></div>
<br><div class="gmail_quote"><div><div>On Fri, Jul 1, 2016 at 9:56 AM, Kevin Smith <span dir="ltr"><<a href="mailto:ksmith@wikimedia.org" target="_blank">ksmith@wikimedia.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div><div><div>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:<br><br></div>1. <b>Sequential dependencies.</b>
For example, if "Implement feature X" needed to be complete before
"Document feature X", then the implementation task would Block the
document task, and the document task would be blocked by the implement
task. <br><br></div>2. <b>Composition relationships/task breakdown.</b>
For example, if "deploy feature X" consisted of "implement feature X"
and "document feature X", then the deploy task might be a parent, while
the implement and document tasks would be subtasks. <br><br></div>Until
recently, phab has used the blocking/blocked by term to cover both
cases. A parent task would be blocked by its subtasks. There was a
command to create a subtask, which would create the appropriate blocking
relationships. <br><br></div>Now, phab uses the parent/subtask
terminology to cover both cases. In the sequential tasks case, the
endpoint would be considered the parent, so in the example above,
"document" would be the parent, and "implement" would be its subtask. Note that a task may have multiple "parents". <br><br></div>A
nice feature they added is the ability to manage the parent/subtask
relationship from either end. While editing a task, you can change its
subtasks or its parents. Previously, you could only edit one direction. <br><br></div>I created T139181 as a task to update our wiki phab documentation.<span><font color="#888888"><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><br>Kevin Smith<br>Agile Coach, Wikimedia Foundation<br></font></span><font><font><i><font color="#888888"><br></font></i></font></font></div></div></div></div></div></div></div></div></div>
</font></span></div>
<br></div></div>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>