Launchpad itself

cannot team restrict emails to go to the team admin

Bug #1012787 reported by Curtis Hovey
46
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Organisations and projects create teams to control things in Launchpad, and they set the membership. the members cannot leave the team, so they get all team emails unless the team owner set a contact address. Canonical for example owns hundreds of teams, so would require hundreds of addresses if it wanted to limit emails to smaller group.

It would be helpful to permit teams to say email go only to the team admins. As a consequence, setting the contact address of a team that admins many teams ensures only one group of people out of many get notifications. There would also be fewer people Launchpad needs to send emails too.

This issue overlaps with (and maybe solves) bug 82663 which requests that users be able to reuse their own email addresses for teams. The owner of a team is the default admin, instead of trying to reuse an email address for a team, the owner can set the team to only send email to admins.

Joey Stanford (joey)
tags: added: linaro
Revision history for this message
Joey Stanford (joey) wrote :

Diogo pointed out bug #156340 is also related to this.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Organisations and large projects construct large hierarchies of teams. Membership changes made by the root teams are sent to all members of the teams, but the members cannot take action, nor can the admins of the member teams. Membership changes are most useful to the direct team admins who can take action.

Revision history for this message
William Grant (wgrant) wrote : Re: [Bug 1012787] Re: cannot team restrict emails to go to the team admin

On 14/06/12 07:05, Curtis Hovey wrote:
> Organisations and large projects construct large hierarchies of teams.
> Membership changes made by the root teams are sent to all members of the
> teams, but the members cannot take action, nor can the admins of the
> member teams. Membership changes are most useful to the direct team
> admins who can take action.

That's not quite true.

Membership notification emails are sent to the admins of the involved
team, and this is problematic when those admins are themselves teams
with lots of members. Anyone who gets the email is, by their team
memberships, an admin of the original team, so they *can* take action.

Revision history for this message
Joey Stanford (joey) wrote :

On Wed, Jun 13, 2012 at 11:11 PM, William Grant <email address hidden> wrote:
> Membership notification emails are sent to the admins of the involved
> team, and this is problematic when those admins are themselves teams
> with lots of members. Anyone who gets the email is, by their team
> memberships, an admin of the original team, so they *can* take action.

That doesn't sync with the examples I sent over to lifeless and sinzui
I don't believe. I have non-admins getting emails.

Revision history for this message
Curtis Hovey (sinzui) wrote :

The notifications about members joining/leaving your team. This is about your team joining and leaving other teams. When the user teams membership changes, all the members of the subteams get the notifications. For example:

Joey Stanford (joey) added Linaro (linaro) (which you are a member of)
as a member of Pig Tails (linaro-pig-tails).
 <https://launchpad.net/~linaro-pig-tails>

--
You received this email because linaro is the new member.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.