-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: dimanche 19 mars 2006 02:38
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
[snip]
I also don't like the idea of making it obligatory to assign an issue
for closing or setting
don't want to deter anybody else from taking a look at it).
-Lukas
Vincent Massol wrote:
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: dimanche 19 mars 2006 02:38
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
[snip]
I also
-Original Message-
From: Lukas Theussl [mailto:[EMAIL PROTECTED]
Sent: dimanche 19 mars 2006 18:46
To: Maven Developers List
Subject: Re: Jira - Issues closed without assignee
I think you misunderstood my point. It was not at all about opening
issues. In brief, I want to be able
On 3/18/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:
SNIP
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
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
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
-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
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
-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
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
SNIP
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
As far as I'm concerned, setting the assignee to yourself when you close
it has been accepted practice for some time (but we don't need to go
back and change all the old ones).
That way, if it is reopened, the person that closed it can deal with it.
- Brett
Arnaud HERITIER wrote:
Hi guys,
I agree. I don't want that we update all closed issues up until now, but
only that we take care to define the assignee from now.
Arnaud
On 3/18/06, Brett Porter [EMAIL PROTECTED] wrote:
As far as I'm concerned, setting the assignee to yourself when you close
it has been accepted practice for
Honestly, apart from statistical purposes, I don't see the point in
having closed issues assigned to somebody at all. Would all the people
who have moved on to m2 take up an old m1 issue if it gets reopened
today? What about people who have left the project? IMO it's the project
14 matches
Mail list logo
