Wed, Nov 15
Mon, Nov 13
Thu, Nov 9
Clarified in standup that this task is a "subtask" of an epic, but not a "[subtask]" of an estimated task that is deliverable in its own right. Updated the title.
@Jdlrobson The team inferred that you are doing the code review for the Web team stuff. Is that right?
Wed, Nov 8
Thanks, @pmiazga . Being a big task is not enough to estimate it if it is still part of another task that has already been estimated (even if the original parent task was grossly underestimated). It defeats the purpose of estimation, and is redundant. The exception is if the task is, in reality, delivering something on top of the first task, rather than on behalf of it. In that case, it should simply not be labeled "subtask". :)
@ovasileva @phuedx @Jdlrobson My understanding is that a "subtask" in the title of a task indicates that it is part of an existing task that already has an estimate. However, this has 8 points on it. Am I missing something?
Fri, Nov 3
Updated via final steps of
I'm not totally sure what this is. Is there a doc that needs review? Needs making?
Wed, Nov 1
Oct 11 2017
Oct 10 2017
I did a git pull, git add . git push hoping that would get me where I needed to be, but something tells me it's more manual than that.
I updated to add the lines
I think you mean step 4? Also, the link in that step takes me to a "Page not found" error.
@ovasileva found this lurking in a hidden column, so I moved it to where you could see it. Feel free to do with it what you need. :)