Should we remove ability to turn on user and bug deletion?

[Dave Williss]

----- Original Message ----- 
From: "Gervase Markham" <gerv at mozilla.org>
To: <developers at bugzilla.org>
Sent: Monday, April 04, 2005 11:37 AM
Subject: Re: Should we remove ability to turn on user and bug deletion?


> Frédéric Buclin wrote:
>> I think that it will be correctly implemented in the very near future, 
>> see bugs 86328 and 288461. I have submitted a patch for each of these two 
>> bugs and now bug deletion is really clean. These patches are awaiting 
>> review but I think they could be checked in this week already.
>>
>> So please do not remove the bug deletion feature!
>
> Fair enough :-)
>
> Should we beef up the "you really don't want to do this" warning on 
> editparams.cgi on the 2.18 branch?
>

Deleting bugs should be OK, given proper warnings and if bugzilla can
resolve dependency lists.  We occasionally want to delete bugs which
are duplicates (rather than just marking them as such).  The occasional
silly bug needs to be deleted from time to time too.  I once had a couple
high-priority bugs that I couldn't get to because another programmer
who's help I required was too busy on a higher priority task.  I logged
those bugs as depending on a new bug who's subject was something
like "Steve is too busy working on ... to help me".  Steve was amused
but the head programmer was not :-)

Deleting users is, IMHO, a Bad Thing.  We have users in our bugzilla
database who were "former users" long before we converted everything
over to bugzilla.  The system records who logged that error and we
want to keep that history.  For users who left after implementing
bugzilla, we want to keep all their comments, attachments, etc.

What we WOULD like is an easy way to disable a user that
would reassign anything that they're assigned, disable their email
notifications, etc.  I wrote a custom script to do this when we
had a programmer quit a couple months ago.  It reassigned all
his Assigned To items back to the default assignee or the component
and any items for which he as the QA contact went back to the
default QA contact for the component.