No way to delete the last task of a bug

Related to bug 45419

This is becoming more of a problem as we're now seeing a few spam bugs cropping up. A good first stage for fixing this bug would be to create some SQL to delete a bug and its dependencies. We can add a UI for that later.

Deleting a bug is quite hard, since it can be linked to a number of things. Why can't we simply mark the bug as invalid, change the summary/description, making the bug private, something else, or a combination of everything? All those things are quite simple to do, and it saves us from having to consider all the corner cases that are involved with actually deleting bugs from the db.

My observation is that part of the problem with spam bugs is the "explosion" of 1 x spam bug report to multiple recipients. Which is always a Good Thing(tm) from a spammers perspective.

Not particularly caring *how* it's done, but we need a way of making a bug "gone" without causing followup emails/notifications sent to the same persons who copped the spam in the first place. Otherwise we're just rubbing salt into the open wound.

"Delete" being an euphemism for "make it go away" :-)
If invalid does this? Great. If not - the problem still exists.

2ndly - I personally don't want to be having to edit bugs manually to remove spam et al text; and click here and click there to make spam go away - that is not scalable even a little. I'm a sysadmin - not a Data Entry Operator. ;-)

One click - gone. Or some variation of, via an approved persons or the like.

As Diogo alluded to, having a one-click spam deletion process is bug 45419.

Untargeting this for the time being. We have the semi-solution that Bjorn suggested above. I don't know if I'll have time to fix this next cycle, but I'll retarget it if I do.