[hibernate-dev] JIRA issue status - Closed v. Resolved
gbadner at redhat.com
Wed Dec 21 02:18:49 EST 2011
----- Original Message -----
> From: "Sanne Grinovero" <sanne at hibernate.org>
> To: "Hardy Ferentschik" <hardy at hibernate.org>
> Cc: hibernate-dev at lists.jboss.org
> Sent: Tuesday, December 20, 2011 12:55:38 PM
> Subject: Re: [hibernate-dev] JIRA issue status - Closed v. Resolved
> I agree as well on interpreting "Closed" as "forever"; AFAIR new
> issues can be linked to the older closed ones so that while a comment
> might not be allowed, it's still possible to point to "follow ups" in
> case of need.
I agree that "Closed" issues should not be reopened. Links should still be possible for identifying duplicates, issues fixed/caused by a closed issued, etc.
> I'm not sure however about enforcing this, but I'm not against it.
> prefer if committers had the option to reopen, it's never nice when
> tools prevent you to fix eventual mistakes.
I think it would be better to make it a convention that closed issues not be re-opened, but to still allow committers to reopen it if an issue was closed by mistake.
After thinking about it more, I thing Hardy is right about allowing comments on closed issues. I'd forgotten that we can actually filter on "Last commented by a user". Aside from comments about problems with a fix, it's good to hear that the fix was verified by a user and it's always nice to get a "thank you" comment. :)
> @Hardy yes we can customize JIRA to a great extent, especially in
> this area.
I think it's a good idea to automatically close resolved issues when the fix is released.
> On the release steps: I'm not sure re Maven plugins, but JIRA has a
> REST API as well for automating transitions. I agree with Hardy that
> I'm not concerned about such a manual step, but in case we want in
> future this could be automated as I think releases should be more and
> more automated, but we can proceed by small steps; I'd expect this to
> be easier with gradle, and maybe Maven plugins exists.
> There definitely is automation in Jenkins which we could use for
> release automation anyway:
> On 20 December 2011 20:18, Hardy Ferentschik <hardy at hibernate.org>
> > Hi
> > On Dec 20, 2011, at 18:17, Steve Ebersole <steve at hibernate.org>
> > wrote:
> >> 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.
> >> * Closed : The issue is considered finished, the resolution is
> >> correct.
> >> Issues which are not closed can be reopened.
> > I agree with this as well. In HV and SEARCH we close the resolved
> > issues after a release. While they are resolved they could be
> > reopened and closed issues cannot be reopened again. A new issue
> > should be created in this case.
> > Closing the issues is a manual process, but I don't see a problem
> > with that. Compared to other time wasters I don't mind the 2
> > minutes this process takes.
> >> 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.
> > What is the problem with comments on closed issues? Some comments
> > might even be useful (aka "had the same problem, fixed now")
> > However, if someone wants to start a new discussion - tough luck.
> > If the comment is legit we tell them to create a new issue and
> > link to it.
> >> Which brings us to... do we really want to not allow Closed issues
> >> to be
> >> reopened? I mean actually remove the transition?
> > That's a possibility. Can you do that in Jira?
> > --hardy
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
More information about the hibernate-dev