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

Sanne Grinovero sanne at hibernate.org
Tue Dec 20 15:55:38 EST 2011


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'm not sure however about enforcing this, but I'm not against it. I'd
prefer if committers had the option to reopen, it's never nice when
tools prevent you to fix eventual mistakes.

@Hardy yes we can customize JIRA to a great extent, especially in this area.

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:
https://wiki.jenkins-ci.org/display/JENKINS/Jira+Issue+Updater+Plugin

Cheers,
Sanne

On 20 December 2011 20:18, Hardy Ferentschik <hardy at hibernate.org> wrote:
> 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




More information about the hibernate-dev mailing list