All bugs in under the Graveyard classification should prevent changes and comments from all users that do not have editbugs
Categories
(bugzilla.mozilla.org :: Bug Creation/Editing, task)
Tracking
()
People
(Reporter: cpeterson, Assigned: glob)
Details
Attachments
(1 file)
I'm the EPM for the Firefox Android team. I'm told that the legacy Fennec bugs in the "Firefox for Android Graveyard" Bugzilla product are getting a lot of spam comments.
Can we disable comments on all bugs in the "Firefox for Android Graveyard" product? These legacy bugs are handy to have for historical reference, but the current Android team doesn't need to comment on them.
All the components in the "Firefox for Android Graveyard" product:
https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox%20for%20Android%20Graveyard
Excellent idea!
Unfortunately preventing comments is a per-bug not per-product flag.
It makes complete sense that all bugs under the Graveyard classification should be closed for comments and other drive-by changes; morphing bug.
|
||
Comment 3•4 years ago
|
||
|
||
Comment 4•4 years ago
|
||
Is this working as expected? Bug 1778841 was moved to Graveyard->Invalid Bugs->General, it was then moved out of there by the bug's creator who presumably doesn't have editbugs. If someone without editbugs can move the bug out of Graveyard can they not simply trivially work around this restriction?
(In reply to Robert Longson [:longsonr] from comment #4)
Is this working as expected? Bug 1778841 was moved to Graveyard->Invalid Bugs->General, it was then moved out of there by the bug's creator who presumably doesn't have editbugs. If someone without editbugs can move the bug out of Graveyard can they not simply trivially work around this restriction?
I'll investigate as this isn't working as expected, however it is actually the desired behaviour.
The goal of this bug is to prevent old legit bugs from being updated; once graveyarded they are effectively read-only archives. Locking down invalid bugs from further updates wasn't and isn't a goal – a bug's reporter must to be able to move a bug out of "invalid bugs" as the automatic classification of spam bugs might incorrectly classify a bug as spam.
I'm not sure what's going on on that bug; I wasn't able to reproduce it locally nor here in production.
Given I've just pushed a PR to explicitly allow this behaviour in Bug 1778935, I'm not going to dig any deeper here.
Description
•