Thanks Noah! I added the comments. "This step should be between In Progress and Resolved. When a developer has submitted the patch for review, the developer should switch from In Progress to In Review. When the review is completed and taken off the review board, the developer should come back to Jira and mark the bug as Resolved. This is for contributors who are not committers.
In Progress should still be able to go directly to Resolved. the committers who don't need to submit patches for review should still be able to go directly to Resolved." Of course, if patch is rejected, the developer should set it back to in progress to indicate they're working on the changes to the patch. --Alex > -----Original Message----- > From: Noah Slater [mailto:nsla...@tumbolia.org] > Sent: Thursday, September 20, 2012 2:23 AM > To: cloudstack-dev@incubator.apache.org > Cc: David Nalley > Subject: Re: Jira workflow... > > To add a new ticket status, infra needs to create a new workflow for us. > > I have opened an infra ticket for this work: > > https://issues.apache.org/jira/browse/INFRA-5294 > > > Alex, could you add some details to that ticket, such as which status should > come before and after. > > Thanks! > > On Mon, Sep 17, 2012 at 10:47 PM, Alex Huang <alex.hu...@citrix.com> > wrote: > > > David, > > > > Is there a way to add a new step to Jira. I think we should add a "In > > Review" step to indicate the bug has been submitted for review for the > > people who needs to do that. It shouldn't be "Resolved" until the > > review has been done. I tried to add it but either I don't have > > permission or I can't find a way to do it. > > > > Thanks. > > > > --Alex > > > > > > -- > NS
