-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
[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
On Tue, Mar 12, 2013 at 04:58:29AM -0700, Sudha Ponnaganti wrote:
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.
Is
Yes - for easier tracking and follow up on pending tasks as there is no other
workflow built in
Sent from Samsung tablet
Chip Childers chip.child...@sungard.com wrote:
On Tue, Mar 12, 2013 at 04:58:29AM -0700, Sudha Ponnaganti wrote:
However, Would like to get the main task in resolved
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
-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
