104169 - Mass-actions

Status: VERIFIED DUPLICATE of bug 26943

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Ben Bucksch (:BenB)]

A lot of bugzilla spam comes from people doing mass-changes. E.g.
- A module owner or default QA contact changes
- New, huge tracking bugs (just got about 100 mails because of the latter, no
  end in sight, hear me Asa?)
- A new component is created and old bugs in other components are moved over.

We need a way to avoid the spam. I see some options:
- Admin + convention
  Some trusted person is specifically powered to make changes without
  bugzilla notification, but is obliged to send notifications via email to
  a certain newsgroup or newsgroups.- Special mass-change feature
  We have some feature where I can do one change and apply it to many bugs.
  Probably that's the "Change several bugs at once" feature, but with the
  following changes:
  - It works in all cases (e.g. when I want to change the Target Milestone for   
    bugs from several different components or assign them to their respective
    default owner)
  - Every relevant bugzilla user is notified exactly once for each change,
    with a lots of bugs to which the change applies.
I prefer the latter.
Sorry, if this is a dup, didn't check.

Please don't push this bug out in the future, these mass-mails are annoying.

Comment 1

[Ben Bucksch (:BenB)]

s/a lots of bugs/a list of bugs/

"- Special mass-change feature" was the 2. option, Mozilla's editor garbled the
linebreak.

Comment 2

[Matthew Tuck [:CodeMachine]]

Yes, I would deprecate any proposal that caused me to miss out on mail I've
asked for.

*** This bug has been marked as a duplicate of 26943 ***

Comment 3

[Ben Bucksch (:BenB)]

Filed second part as bug 109339.

VRFY.