GNOME Bugzilla – Bug 89889
Bulk (mass) changes in one email/bugmail notification (for "spammy" changes)
Last modified: 2018-06-16 13:28:19 UTC
it would be nice if there was a checkbox somewhere that allowed somebody changing the bug to mark the change as "spammy", ie the kind of thing a maintainer doesn't want to see. in the case of nautilus, bug volunteers are currently changing the subject to "[SPAM] ..." to allow client-side filtering, but something like this could be combined with 2.16 server-side filtering, and doesn't involve modifying the bug. There would have to be some sort of trusted group for doing this, to prevent untrusted people from changing bugs silently.
it might also be worth restricting the type of thing that can be marked spam. Closing things as WONTFIX, for example, probably should go to maintainers, but closing as NOTGNOME probably shouldn't.
random thoughts: Worrying about limiting the option is more work than dealing with the random people who abuse it as it happens (since they'd already need permissions to change the bug anyways). This in my opinion is two different bugs. First, there's the mass "SPAM resetting all the milestones" changes or whatnot. What would be more useful for bugs like these is (instead of having no mail at all), having a "summary" email, that lists the changes, and all the bug-ids. This significantly reduces the s/n ratio, and hopefully turns it into something maintainers want to see. Second, there's the stupid stuff (FIXED NOTGNOME, adding yourself as a cc), that's useless for some category of people to see. Bugzilla already has an interface for managing what kinds of emails you wish to get, it's just not comprehensive enough so you can go in and tweak that sort of stuff. So, what would the level of detail be to solve that issue? My personal pet peeve is the cc emails, but (campd) can you weigh in with other types of things you might not want to see?
This is available in 2.17.x (per the RH bugzilla). I guess it's not in 2.16, but I'm all for skipping that release series anyway.
Upstream has a patch at: https://bugzilla.mozilla.org/show_bug.cgi?id=23924 Hasn't passed review, waiting for that.
Probably what will happen instead is that mass-changes will send a single email. I think we have a bug for that somewhere.
https://bugzilla.mozilla.org/show_bug.cgi?id=23924 is WONTFIX. https://bugzilla.mozilla.org/show_bug.cgi?id=26943 would be the approach to use.
Mozilla finally fixed this on https://bugzilla.mozilla.org/show_bug.cgi?id=1062718, unfortunately for version 6.0.
After https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure , GNOME is moving its task tracking from Bugzilla to GitLab at https://gitlab.gnome.org/ as previously announced in https://mail.gnome.org/archives/desktop-devel-list/2018-May/msg00026.html . See https://wiki.gnome.org/GitLab for more information. Hence closing this ticket as WONTFIX: There are no plans to work on Bugzilla.