However, Would like to get the main task in resolved state as well once dev task is done. Otherwise QA would not know which user stories that we need to follow-up on as QA and Doc tasks depend up on Dev task completion.
-----Original Message----- From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] Sent: Monday, March 11, 2013 11:59 PM To: cloudstack-dev@incubator.apache.org Subject: RE: [QUERY] Resolving JIRA ticket when sub task tickets are present > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Tuesday, March 05, 2013 8:09 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: [QUERY] Resolving JIRA ticket when sub task tickets are > present > > On Tue, Mar 05, 2013 at 10:42:23AM +0530, Sateesh Chodapuneedi wrote: > > Looking for best practice to follow when resolving a feature ticket > > in ASF > JIRA. > > If a feature branch has QA and DOC sub task tickets which are still > > open and > development is complete, should the feature ticket kept open or > resolved/fixed? > > Or create another sub task for development mark that sub task as > resolved? > > Kindly suggest. > > > > Regards, > > Sateesh > > > > IMO, we would create a "dev" sub-task and track completion of the code > there. The parent should stay "in progress" until all sub-tasks are done. [Animesh>] Agreed. Let's follow that for 4.2. > > If we don't do child development tasks, then I would still keep the > parent as "in progress" until docs and QA are done. The feature isn't > *done* until it's tested and documented. > > -chip
