Using "In Progress" status in JIRA

[Animesh Chaturvedi <an...@citrix.com>]

Folks

It seems that we do not use "In Progress" status in JIRA as often as we should. Issues seem to change from "Open" to "Resolved" directly. IMHO marking an issue "In Progress" provides much better visibility and helps communicate to community that you are working on that item.

If for whatever reason you stop working on that item and will not attend to it you can always mark it back as "Open".

For 4.2 I see that 40 features/ improvement tickets changed from "Open" to "Resolved" directly. And for Bugs "509" bugs moved from "Open" to "Resolved" directly.


Thanks
Animesh

Re: Using "In Progress" status in JIRA

[Chip Childers <ch...@sungard.com>]

On Fri, Jun 14, 2013 at 08:00:33AM +0000, Koushik Das wrote:
> 
> > -----Original Message-----
> > From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> > Sent: Friday, June 14, 2013 6:32 AM
> > To: dev@cloudstack.apache.org
> > Subject: Using "In Progress" status in JIRA
> > 
> > Folks
> > 
> > It seems that we do not use "In Progress" status in JIRA as often as we
> > should. Issues seem to change from "Open" to "Resolved" directly. IMHO
> > marking an issue "In Progress" provides much better visibility and helps
> > communicate to community that you are working on that item.
> > 
> 
> Isn't assigning a bug would also mean the same? The 'In Progress' is useful when bugs are triaged on a daily basis, most probably towards end of a release cycle.
> 
> > If for whatever reason you stop working on that item and will not attend to it
> > you can always mark it back as "Open".
> > 
> 
> If someone has stopped working on a bug simply unassign so that anyone else can pick it up.
> 
> > For 4.2 I see that 40 features/ improvement tickets changed from "Open" to
> > "Resolved" directly. And for Bugs "509" bugs moved from "Open" to
> > "Resolved" directly.
> > 
> 
> I don't see any issues in that.

+1 if it's a quick fix / change.  IMO, setting the In Progress status is
a "nice thing to do for the community" when something is going to take a
long time to work on.

> 
> > 
> > Thanks
> > Animesh
> 

RE: Using "In Progress" status in JIRA

[Koushik Das <ko...@citrix.com>]

> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Friday, June 14, 2013 6:32 AM
> To: dev@cloudstack.apache.org
> Subject: Using "In Progress" status in JIRA
> 
> Folks
> 
> It seems that we do not use "In Progress" status in JIRA as often as we
> should. Issues seem to change from "Open" to "Resolved" directly. IMHO
> marking an issue "In Progress" provides much better visibility and helps
> communicate to community that you are working on that item.
> 

Isn't assigning a bug would also mean the same? The 'In Progress' is useful when bugs are triaged on a daily basis, most probably towards end of a release cycle.

> If for whatever reason you stop working on that item and will not attend to it
> you can always mark it back as "Open".
> 

If someone has stopped working on a bug simply unassign so that anyone else can pick it up.

> For 4.2 I see that 40 features/ improvement tickets changed from "Open" to
> "Resolved" directly. And for Bugs "509" bugs moved from "Open" to
> "Resolved" directly.
> 

I don't see any issues in that.

> 
> Thanks
> Animesh