Or do we want to go to a system where we only create tasks to test/document features that are completed? That might make it easier for the manager to see what's really still pending.
On Tue, Feb 5, 2013 at 3:02 PM, Animesh Chaturvedi <animesh.chaturv...@citrix.com> wrote: > > >> -----Original Message----- >> From: Marcus Sorensen [mailto:shadow...@gmail.com] >> Sent: Tuesday, February 05, 2013 1:53 PM >> To: Animesh Chaturvedi >> Cc: cloudstack-dev@incubator.apache.org >> Subject: Re: [ACS41] Can folks please take responsibility for updating their >> own >> Jira tickets? >> >> Someone created sub-tickets for ours (QA, etc). It doesn't feel right to >> close >> them until those pending subtasks are also completed. I made a comment that >> the features were completed and merged, and assumed that the owners of the >> sub tasks would update the ticket as well. >> > [Animesh>] Yes agreed they need to be closed when those subtasks are done by > their respective owners > >> So perhaps at least some of it is just understanding how the flow is >> supposed to >> work. >>
