What is the policy about JIRA "resolved" versus "closed" tasks?

[Martin Desruisseaux <ma...@geomatys.fr>]

Hello all

I'm in the process of reviewing JIRA tasks. Except for 3 tasks, we have 
only "resolved" tasks, no "closed" tasks. This include many tasks from 
0.1-incubating and 0.2-incubating releases. So I wonder, when tasks are 
closed?

I initially though that tasks were first resolved, then closed at some 
later stage when we get confirmation from one or many users that the fix 
solved their problem. However previously closed tasks have seen their 
status changed to "resolved", which made me though that maybe the policy 
is to close the tasks only when a release is made. Is that the case? If 
so, I wonder what is the plus value of "resolved" / "closed" status 
compared to the "release fixed" field?

     Thanks,
     Martin

Re: What is the policy about JIRA "resolved" versus "closed" tasks?

["Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>]

Hi Martin,

-----Original Message-----

From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Tuesday, July 2, 2013 10:28 AM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Re: What is the policy about JIRA "resolved" versus "closed"
tasks?

>Le 01/07/13 23:58, Mattmann, Chris A (398J) a écrit :
>> My biggest feeling about Resolved / Closed is that once you close
>> an issue, you can't edit it without reopening it.
>
>It seems that an option exists for allowing edition of closed issues
>[1]. However I didn't found how to enable it in the SIS JIRA
>administration panel.

Yeah it's possible ASF infra would allow us to enable this; it's
also possible they wouldn't. I also didn't even know about that
option which suggests at least to me since I've used JIRA for quite
a while that it's not a super well known option :)

>
>> We've had several
>> closed issues before where in fact later we've had to go back and
>> update them (change an assignee; change a Fix or Affects version, etc.)
>> Because they are "Closed" they can't be edited. So, in turn I favor
>> using "Resolved" as the fixed issue status. Resolved issues can
>> still be updated, so they don't require a re-open and re-close.
>
>Do you mean for fixing some fields that we forgot to fill properly in
>the first place (e.g., if we forgot to fill the "fix version" field)?
>Could the assignee takes care of that when he starts the work, since he
>is likely to see and comment on the task anyway? If the editions are
>bigger than fixing incorrect fields, would it be a case for re-opening
>the task or creating a new one?

Agreed in a perfect world this can be taken care of using the above
process -- but what I find quite often is that once an issue is closed,
(say months earlier by someone else besides the RM), as the RM you find
having to update JIRA or update fix versions or Bulk Change issues. Bulk
change issues won't work on issues that are already closed, but does
work on those that are Resolved. So in practice I've found Resolved to
be a "safe" resolution -- it indicates the issue is fixed, but is still
modifiable practically which may be needed down the road.

>
>It is still possible to comment on closed tasks, or to clone them or
>create links to new tasks. For some tasks where it would be hard to fit
>additional work in the task description, additional work would rather be
>"follow up" tasks or similar tasks applied in other context. In such
>cases, would creating a new task (possibly by cloning the closed one)
>and linking it to the closed task be a workable approach?

Cloning is an option -- have never tried that and will look into it.
In the meanwhile, I don't think there should be a policy here -- if you
feel strongly that Closed issues make sense, by all means go for it. I'll
continue to mark mine as Resolved in the potential case they need to be
modified later :) Either one is great.

Cheers,
Chris

>
>     Cheers,
>     Martin
>
>
>[1] 
>https://confluence.atlassian.com/display/JIRA/Allow+editing+of+Closed+Issu
>es
>

Re: What is the policy about JIRA "resolved" versus "closed" tasks?

[Martin Desruisseaux <ma...@geomatys.fr>]

Le 01/07/13 23:58, Mattmann, Chris A (398J) a écrit :
> My biggest feeling about Resolved / Closed is that once you close
> an issue, you can't edit it without reopening it.

It seems that an option exists for allowing edition of closed issues 
[1]. However I didn't found how to enable it in the SIS JIRA 
administration panel.

> We've had several
> closed issues before where in fact later we've had to go back and
> update them (change an assignee; change a Fix or Affects version, etc.)
> Because they are "Closed" they can't be edited. So, in turn I favor
> using "Resolved" as the fixed issue status. Resolved issues can
> still be updated, so they don't require a re-open and re-close.

Do you mean for fixing some fields that we forgot to fill properly in 
the first place (e.g., if we forgot to fill the "fix version" field)? 
Could the assignee takes care of that when he starts the work, since he 
is likely to see and comment on the task anyway? If the editions are 
bigger than fixing incorrect fields, would it be a case for re-opening 
the task or creating a new one?

It is still possible to comment on closed tasks, or to clone them or 
create links to new tasks. For some tasks where it would be hard to fit 
additional work in the task description, additional work would rather be 
"follow up" tasks or similar tasks applied in other context. In such 
cases, would creating a new task (possibly by cloning the closed one) 
and linking it to the closed task be a workable approach?

     Cheers,
     Martin


[1] 
https://confluence.atlassian.com/display/JIRA/Allow+editing+of+Closed+Issues

Re: What is the policy about JIRA "resolved" versus "closed" tasks?

["Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>]

Hey Martin,

My biggest feeling about Resolved / Closed is that once you close
an issue, you can't edit it without reopening it. We've had several
closed issues before where in fact later we've had to go back and
update them (change an assignee; change a Fix or Affects version, etc.)
Because they are "Closed" they can't be edited. So, in turn I favor
using "Resolved" as the fixed issue status. Resolved issues can
still be updated, so they don't require a re-open and re-close.

So my +1 to use Resolved instead of Closed.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Monday, July 1, 2013 3:32 AM
To: Apache SIS <de...@sis.apache.org>
Subject: What is the policy about JIRA "resolved" versus "closed" tasks?

>Hello all
>
>I'm in the process of reviewing JIRA tasks. Except for 3 tasks, we have
>only "resolved" tasks, no "closed" tasks. This include many tasks from
>0.1-incubating and 0.2-incubating releases. So I wonder, when tasks are
>closed?
>
>I initially though that tasks were first resolved, then closed at some
>later stage when we get confirmation from one or many users that the fix
>solved their problem. However previously closed tasks have seen their
>status changed to "resolved", which made me though that maybe the policy
>is to close the tasks only when a release is made. Is that the case? If
>so, I wonder what is the plus value of "resolved" / "closed" status
>compared to the "release fixed" field?
>
>     Thanks,
>     Martin
>