> > I think in Jira the coupling is relatively loose, I was talking more > about sub-tasks as a concept. If I had a task to bring a birthday cake > to your party, and I had sub tasks of 'baking the cake', 'decorating > the cake', and 'delivering the cake', then the task wouldn't be > completed properly until I had done all three. We have a cake, the > code has been committed, but it's not decorated. We could bring it to > the party, but it wouldn't be pretty. Perhaps there should have been a > sub-task to code/commit the solution, although I'm not sure how > granular we want to get.
If every example can be as vividly illustrated as this, it would solve lots of communication problems. :) I wonder what analogy will you give to having a subtask to cherry-pick the fix to another release? --Alex
