376637 - Allow administrators to drop tickets and attachements easily when facing spam

Status: RESOLVED WORKSFORME

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[guillomovitch]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.3) Gecko/20070208 Mandriva/2.0.0.3-2mdv2007.1 (2007.1) Firefox/2.0.0.3
Build Identifier: 

Someone abused bugzilla to post porn content as attachements. The only way to get rid of it was to delete related entries directly from the database, in the following tables:
- bugs
- bugs_activity
- attachements
- attach_data

An admin-reserved 'purge' action would be handy in this case.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[guillomovitch]

LPSolit just told me about the attachement deletion setting. However, deleting 17 attachments one by one is still painful, hence the need to drop the ticket directly.

Comment 2

[Max Kanat-Alexander]

As you said, you can already delete attachments.

You can delete bugs by moving them into a particular product and then deleting that product.

Comment 3

[guillomovitch]

I already tried that solution, it doesn't work: as long as you have bugs attached to a product, you can't delete it. And anyway, it would only be a workaround, not a clean solution.

Comment 4

[Max Kanat-Alexander]

You need to turn on the "allowbugdeletion" parameter.

Comment 5

[guillomovitch]

Ahhh....
May I still object it is non-intuitive, painful (you have to create a trash product each time, transfer your bug, then delete it), and really a poor workaround ?

Comment 6

[Frédéric Buclin]

Deleting a bug shouldn't be a straightforward process. Too dangerous IMO. You can restrict the "Trash" product to admins, so that nobody else is annoyed with these bugs. And admins would know to ignore bugs being in this product (and why not delete the product once per month or so). Actually, it's easier to delete and recreate a component than a product. So you should rather have a Trash component, not product.

Comment 7

[guillomovitch]

As long as you'll have to create pseudo-items in order to clean up your base from adverse content, it will be an ugly hack. You'll end up with admins cleaning up their database directly (with far much risks) if you persist telling them what is dangereous and what is not.