Launchpad itself

Possible to Stop Bug Notifications for Team Members?

Asked by David Graf

Hey
I would like to stop the email notification for team members when a bug is created/modified. Only the assignee and the submitter should get an email. But the team should still be related to the bug. Is that possible? My team members complain about the amount of emails they get.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Curtis Hovey
Solved:
Last query:
Last reply:
Revision history for this message
Brad Crittenden (bac) said : 		#1

If your team is listed as the bug supervisor then that team will be notified when new bugs are filed.

You can, however, set a contact email address for the team and all email for the team will be sent to that address. The address can be your address or a mailing list. In that case, only those people get notified of new bugs but individuals will be notified when they are assigned or subscribed to bugs.

Members of the bug supervisor team will still be able to see private bugs using this arrangement.

Revision history for this message
David Graf (davidagraf) said : 		#2

Hey
I set up the team mail address alternative. But unfortunately, the archive of the team mailing is not restricted. Everybody can read the notifications of our private bugs. Is it possible to restrict the team mail address?

Revision history for this message
Best Curtis Hovey (sinzui) said : 		#3

No it is not. Launchpad does not handle mailing lists well. A team with a mailing lists is meant for communitication, not control. Many project create separate teams representing control and communication aspects. Project owners, drivers and bug supervisors can be teams with mailing list, but only if the team agrees that every one should be getting the emails. Create a team without a mailing list is probably to correct answer. Some people create teams with an email address that will never be checked and set that team as the bug supervisor, guaranteeing that each member has full access to a bug without ever being notified about the desciuptions.

Revision history for this message
David Graf (davidagraf) said : 		#4

Thanks Curtis Hovey, that solved my question.