Here is part 3 again: 3. "B" commits the change and fixes the issue. Now "B" wants to close the issue, a. Is it a requirement by JIRA or OpenEJB that "B" has to assign the issue to himself first before closing it ? b. If not, then what is the value behind "B" (or somebody else) assigning an issue to "B" and then closing it (I think I have seen something similar being done in past when I used to contribute a patch, a committer would first assign the issue to me, commit and close the issue)
On 9/15/07, David Blevins <[EMAIL PROTECTED]> wrote: > > On Sep 15, 2007, at 9:11 AM, Karan Malhi wrote: > > > Below is a question regarding unassigned issues . > > > > Here is a scenario > > > > 1. "A" opens an issue and it is unassigned > > 2. "B" starts working on it (issue still unassigned) > > 3. "B" commits the change and fixes the issue. Now "B" wants to close > > the issue, does "B" have to assign the issue to himself first before > > closing it ? If not, then what is the value behind assigning an issue > > to "B" and then closing it (I think I have seen this happen in past > > commits) > > Sorry, my brain read that last part as "should B assign to B, if not > why should B assign to B" > > What's the question? > > -David > > -- Karan Singh Malhi
