Vincent Massol wrote:
-----Original Message-----
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:50
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Vincent Massol wrote:
-----Original Message-----
From: Alan D. Cabrera [mailto:[EMAIL PROTECTED]
Sent: samedi 18 mars 2006 17:31
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
Arnaud HERITIER wrote:
Hi guys,
I noticed that we have in maven projects (particularly in m1) a lot
of
issues closed (2033) but without assignee (698).
I think that it is a good practice to assign the issue to the one
who
closed it (even if it's a Won't fix or duplicated status).
It's easier to see who closed it (in an issues list for example). We
don't
have to open the issue to see the change history.
WDYT ?
Arnaud
What is the use case for seeing who closed the issue w/out actually
opening that particular issue up?
Actually I believe we should simply configure jira to not allow an issue
to
be closed without an assignee. The same should apply for not specifying
a
"fix for" field, etc. Those fields should be defined as mandatory. Not
sure
how to do this with jira but I supposed it's possible.
I think that this requires a custom plugin that's easy enough to
implement.
However, I think that my question still remains to be answered. IMHO,
it's better to see at a glance what the final disposition of the issue
was, i.e. that it was assigned to no one or that it was assigned to
someone other than the closer, than to have it artificially set to the
closer.
I think that whoever is closing it is handling it defacto. Deciding to close
it even with a won't fix is still hanlding it.
Ahh, good idea.
Regards,
Alan
