Too easy to spam a team by assigning a bug to them

[Jonathan Lange]

This is very closely related to bug 100080 -- maybe even a duplicate.

It's too easy to spam a large team by assigning them to a bug. One very common case is:
  * I've found a bug in the package
  * I'll file the bug and assign it to the maintainer (generally a large team on Ubuntu packages)

Bug 100080 suggests an "are you sure" page for big teams. That might work, although it's quite probable that users will just click-through.

Other possibilities are adding config options preventing teams from being assigned to bugs, or somehow restricting who can assign bugs & how. (e.g. if you aren't on the bug contact team, you can only assign bugs to yourself, or to individuals or something).

[Sarah Kowalik (hobbsee-deactivatedaccount)]

https://bugs.launchpad.net/bugs/287244 is another example of this happening - which spammed 55 people, completely needlessly.

The solution we came up with in #launchpad was to forbid assigning teams to bugs until you're in ubuntu-quality (or whatever the team is in the other projects that do that is)- ie, restrict it in the same way that importance is.

[Eleanor Berger (intellectronica)]

> or somehow restricting who can assign bugs & how

I think that's the solution, although I wouldn't exclude disqualifying teams from being assigned bugs if that's not something projects use.

[Martin Albisetti (beuno)]

Live from UDS Mountain View, this is really a big pain point, and I think that either of these solutions will work:
- As Sarah proposes, only let users with permissions to assign a bug to a team
or
- Let each project set the policy. This is kinda hard to do, so the first bit is probably a sane way to start.

[Brian Murray (brian-murray)]

This bug is a duplicate of bug 511269 (only bug supervisor should be able to assign bugs to other people) which is now Fix Released on production.