[Tracker-discuss] [issue302] make 'closed' issues read-only
R David Murray
metatracker at psf.upfronthosting.co.za
Sat Oct 10 18:29:29 CEST 2009
R David Murray <rdmurray at bitdance.com> added the comment:
On Sat, 10 Oct 2009 at 16:06, Ronald Oussoren wrote:
> I've noticed several time in the patch that users add new unrelated information
> to issues that are already closed, instead of opening a new issue.
> This is unhelpful because the new issue might go unnoticed, and because it
This is true. Some bug trackers auto-open an issue when new information
is added. I'm not sure that this is a good idea, but it is a
> mudles the news file. That is, if a news file notes "Fixes issue 1234" it is not
> immediately clear if this refers to the original issue or the new message added
> to the end of an already resolved one.
If the committer follows the convention of noting the revision in which
the fix was committed, then it is pretty clear from scanning the issue
what was fixed (that is, anything after the message giving the commit
info was _not_ dealt with).
> I would therefore prefer if issues were read-only once closed, but probably not
> for developers in the "Assigned to:" list and also not for people on the nosy
I don't think I've run into any other bug tracker that works this way,
and I'm not sure it is a good idea. Specifically, if someone other than
the interested parties discovers that the fix did not work (perhaps on a
platform the original parties did not test on), or caused a new problem,
then the original issue is usually the appropriate place to report it
(and those on the nosy list will get notified, which mitigates the
"closed issue not noticed" problem).
status: unread -> chatting
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
More information about the Tracker-discuss