[hibernate-dev] JIRA issue status - Closed v. Resolved

Steve Ebersole steve at hibernate.org
Tue Dec 20 12:17:42 EST 2011

We seem to have a few different understandings of Closed versus Resolved 
as a status.  We should come to a consensus.

According to Atlassian...
* Resolved : A resolution has been taken, and it is awaiting 
verification by reporter. From here issues are either reopened, or are 
* Closed : The issue is considered finished, the resolution is correct. 
Issues which are not closed can be reopened.

For the most part I agree with these definitions.

The first thing to notice is that these definitions say (imply) that a 
Closed issue cannot be reopened.  Today, we do allow that.  Do we really 
want to not allow closed issues to be reopened?  Partially this relies 
on a few other decisions...

Should all issues that are part of a release be Closed?  After an issue 
has been part of a release, the normal process to do additional work on 
the issue is to open a new issue.  Mainly that is to keep release notes 
straight.  Unfortunately, as far as I can tell this would have to just 
be a manual release step to transition all Resolved issues to Closed. 
But I think from a release tracking perspective this is the most correct 

Comments.  Today we allow comments on Closed issues.  Unfortunately we 
have to reopen the issue to then delete comments.  So if we no longer 
physically allow Closed issues to be reopened, then IMO we should 
certainly not allow comments on Closed issues.

Which brings us to... do we really want to not allow Closed issues to be 
reopened?  I mean actually remove the transition?  Or do we just want to 
say that as a standard procedure we do not reopen Closed issues?

steve at hibernate.org

More information about the hibernate-dev mailing list