Comment 22 for bug 659947

On 17 March 2011 22:38, Robert Collins <email address hidden> wrote:
>> Confused or malicious users can and do make random changes to bugs, and
>> people seem to cope with them by reverting them, gently correcting the
>> user, or admin intervention.  Is setting it to Triaged in particular
>> need of protection?
>
> We regularly get cases where one person doing their own view of the
> 'right thing' causes many hours or days worth of work for core devs
> undoing that persons changes. LP doesn't throttle folk making lots of
> changes, and this makes social training ineffective fairly often.
> Additionally LP's habit of not letting mistakes be undone means bugs
> accrue lots of noise. (Look at bug 1, for instance).

Yes, I agree very much that this does occur and does cause problems.
Also I think Launchpad could do some things to discourage noise
changes and to make them easier to undo.

But I question whether having a specific restriction around the
Triaged state is really helping with this.

A misguided change into the Triaged state is no more harmful than
other changes people can make (eg Triaged->Invaild, Confirmed->Fix
Released) and it is trivial to undo (by contrast to eg adding
comments).

In fact, the presence of this mechanism makes noise changes to status
more harmful, because only privileged developers can undo some of
them.