can't unsubscribe from team-related bug-activity emails

Note: this is not a duplicate of Bug #75620, as that bug deals with the question of how one can unsubscribe from individual bugs, whereas this bug is about unsubscribing from *ALL* bugs which might be sent due to team-membership.

It also appears that nothing will be done with #75620, since it is almost 3 years old, and not very clearly reported.

This is a problem that we're aware of and which we do plan to tackle, essentially by allowing you to tell Launchpad that you specifically don't want to receive email about a particular bug.

While opting-out of mail for a particular bug is a fine feature, I would really recommend having an 'opt-out' of ALL bug-related mail. The objective of this request is to avoid having to receive any bug-related mail (I would prefer to browse bugs on Launchpad directly). If the only change made to Launchpad permits a bug-specific opt-out, then this is of little value to me, because I still will continue to receive bug related mail, even if I don't want it. Yes, I can go and click to opt out of every new bug-report which is filed, but that is an annoying waste of time I'd prefer to avoid.

Of course I can just auto-delete all bug-related mail with my mail client, but that's a waste of bandwidth, and simply a workaround for a feature which I believe should be there.

The point is to save people time, by not forcing them to get mail they don't want to receive, and not forcing them to jump through hoops every time a new bug is filed in order to stop mail being sent to them.

2009/2/16 Mark Edgington <email address hidden>:
> While opting-out of mail for a particular bug is a fine feature, I would
> really recommend having an 'opt-out' of ALL bug-related mail.

I think that's a reasonable request, maybe we should implement this, but ...

> Of course I can just auto-delete all bug-related mail with my mail
> client, but that's a waste of bandwidth, and simply a workaround for a
> feature which I believe should be there.

... that's, in a way, how Launchpad's notification system is designed.
The mailing services provides detailed metadata in the headers (and
even in the body) so that you can have complete control over the
notifications you receive from Launchpad. I don't think that the
bandwidth is really much of a problem. Even the thinest connections
nowadays can easily cope with the load that Launchpad's textual
messages generate.

2009/2/16 Mark Edgington:
> While opting-out of mail for a particular bug is a fine feature, I would
> really recommend having an 'opt-out' of ALL bug-related mail. The
> objective of this request is to avoid having to receive any bug-related
> mail (I would prefer to browse bugs on Launchpad directly). If the only
> change made to Launchprad permits a bug-specific opt-out, then this is of
> little value to me, because I still will continue to receive bug related
> mail, even if I don't want it. Yes, I can go and click to opt out of
> every new bug-report which is filed, but that is an annoying waste of
> time I'd prefer to avoid.

The idea is that we'll provide what we loosely term an "ignore"
subscription. That is your relationship with bugs you report / are
assigned to / comment on will be the same as it always was but you
choose not to receive email. Given the way that Launchpad
subscriptions work there's no reason we can't apply this globally as
you suggest.

--
Graham Binns | PGP Key: 4DAD18FA

Still important to do I think, and we came close but didn't quite get there in the better bugs notification story. The next big hope is the notification service concept, which could give use a systematic fix to a wide range of related bugs.