Bertrand Delacretaz wrote: > On Fri, Sep 4, 2009 at 2:48 PM, Jukka Zitting<[email protected]> wrote: >> On Fri, Sep 4, 2009 at 2:44 PM, Bertrand >> Delacretaz<[email protected]> wrote: >>> On Fri, Sep 4, 2009 at 2:31 PM, Felix Meschberger<[email protected]> wrote: >>>> ...At the same time I think it would be a good idea to >>>> prevent bugs from being reopened as has been set on Jackrabbit and other >>>> projects... >>> What's the idea behind this? Force people to reopen new issues if a >>> problem is not really solved? >> In Jackrabbit we mark issues as Resolved when the fix is in trunk, and >> Closed when the fix has been released. >> >> Once the fix has been released, it can no longer be changed and thus >> it's better to prevent people from reopening the issue. A new issue >> with the correct Affects Version setting should be created in such >> cases. > > Ok, I see the idea and agree. Though...if someone mistakenly changes > an issue to "Closed", is it dead? Or can an administrator change it > back? > Hmm, usually I close an issue if I think it's completly fixed :) But I usually do this before the release. Maybe I'm using a wrong workflow...
But anyway, I think it should always be possible to reopen a bug, even if the fix has been released. But on the other hand, I guess, we all are working slightly different with (Jira) issues which makes it even harder :) I personally don't think that we need new states for documentation or testing. Usually people are either doing this anyway, or are never doing it - so a new state doesn't help. Carsten -- Carsten Ziegeler [email protected]
