Closed Bug 1044412 Opened 10 years ago Closed 10 years ago

create a graveyard for invalid testing bug reports

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: wsmwk, Assigned: dkl)

Details

We should have a graveyard for bugs reports that we are marking INVALID and don't belong in legitimate products and components. I am referring mainly to bugs created by people testing their bugzilla foo in b.m.o instead of using landfill, but also just outright spam.

A side benefit of putting these bugs in a graveyard is the bugs will stop showing up in a product's search results and statistics.

Bonus points for creating some automatic mechanism that locks the reporter's account and/or sends them some form of automated mail, so that the person closing the bug report doesn't need to be writing the explaination.
(In reply to Wayne Mery (:wsmwk) from comment #0)
> We should have a graveyard for bugs reports that we are marking INVALID and
> don't belong in legitimate products and components. I am referring mainly to
> bugs created by people testing their bugzilla foo in b.m.o instead of using
> landfill, but also just outright spam.
> 
> A side benefit of putting these bugs in a graveyard is the bugs will stop
> showing up in a product's search results and statistics.

I have created a new product called "Invalid Bugs" with a single component "General". We
can now use this as a holding place for these types of bugs. Please tell the world.

dkl
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Windows Vista → All
Hardware: x86 → All
Resolution: --- → FIXED
Thanks David.  

But, as best I can determine none of the products in classification "Graveyard" are Product list in user facing BMO
Flags: needinfo?(dkl)
(In reply to Wayne Mery (:wsmwk) from comment #2)
> Thanks David.  
> 
> But, as best I can determine none of the products in classification
> "Graveyard" are Product list in user facing BMO

I think I had a setting incorrect so you should be able to see it now.

dkl
Flags: needinfo?(dkl)
You need to log in before you can comment on or make changes to this bug.