Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # dev >> RESOLVED vs CLOSED

Copy link to this message
I think that we're using RESOLVED in place of CLOSED as Apache JIRA is configured in a way that it actually won't allow to reopen or edit any JIRA in CLOSED state to anyone other than reporter itself. We had issues in the past when we needed to change the "fixVersion" field, but we couldn't as the jira was CLOSED.


On Wed, Apr 03, 2013 at 11:45:49PM -0400, Israel Ekpo wrote:
> Team,
> I have noticed some issues are in RESOLVED state and others are in CLOSED
> state.
> I wanted to find out when we can use RESOLVED and when we can used CLOSED
> for the status of an issue.
> For instance, some issues have been marked as resolved for 12 months or
> longer.
> https://issues.apache.org/jira/browse/FLUME-1015
> https://issues.apache.org/jira/browse/FLUME-215
> https://issues.apache.org/jira/browse/FLUME-694
> A quick lookup on these JIRA statuses suggest that:
> Implies that a resolution has been taken, and it is awaiting verification
> by reporter. From here issues are either reopened, or are closed.
> Implies that the issue is considered finished, the resolution is correct.
> Issues which are closed can be reopened.
> I think we should go over some of the issues that are marked as RESOLVED to
> see if thier status should be set to CLOSED.
> Here are some 800+ issues in RESOLVED state
> http://bit.ly/XYZ3Vz
> It looks like RESOLVED is not the final state these issue should be. If the
> reporter believes that the issue has been addressed satisfactorily, it
> should be marked as CLOSED.
> Any thoughts?