Launchpad sends change notification updates to the person who requested the change

For example it's pointless to send an update status mail to my mailbox for comments I have sent on some bug I'm subscribed.

it's a bit frustrating... I look at my bug folder mailbox and it says I have 7 bugs, so I resolve all 7 and the box is empty, then 15 minutes later I have 10 or 11 things in there because I closed, commented or assigned bugs. Its like the more work I do the more work I have to do. :-(

I use the following sieve rule to work around this bug:

# My own comments in Launchpad bugs
if allof(
        header :contains "Reply-To" "@bugs.launchpad.net>",
        header :contains "From" "<mdz@"
 ) {
        discard;
}

This is really a very annoying behaviour. First I thought, I just have to configure it somewhere in Launchpad, like you can configure those things on other platforms. I took a while for me to discover that this behaviour can not be configured. Very annoying. Would be great if this could be fixed.

On Mon, Apr 06, 2009 at 08:48:38AM -0000, Mark wrote:
> This is really a very annoying behaviour. First I thought, I just have
> to configure it somewhere in Launchpad, like you can configure those
> things on other platforms. I took a while for me to discover that this
> behaviour can not be configured. Very annoying. Would be great if this
> could be fixed.

Adding a configuration option would probably be the best way to tackle
this, since quite a few people (me included) find it an extremely useful
feature.

What about this feature request? Is someone working on that?

I would really appreciate this to be done.

One case where this occurs is when someone assigns themselves a bug report - they receive the full bug details since they are a new subscriber (see _send_bug_details_to_new_bug_subscribers). Looking at the acter (who assigned the bug) parameter I am adding may be one way to prevent that email from being sent.

It is also pointless to send me an email that tells me that a branch was linked to a bug when I commited with the --fixes option. And the same is true for blueprints or merge proposals, one should not get an email for any action that was done by themselves.

On 23 January 2011 18:03, Martin Ueding <email address hidden> wrote:
> It is also pointless to send me an email that tells me that a branch was
> linked to a bug when I commited with the --fixes option. And the same is
> true for blueprints or merge proposals, one should not get an email for
> any action that was done by themselves.

This is a matter of personal preference: some people like to have a
complete record in their mail, including actions they did themselves.
But there should be a way to turn it off.

--
Martin

This feature can be incorporated into our work with bug subscriptions and filters.

r10178 in db-stable (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/10178) is part of this bug's fix.

Fixed in stable r12339 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12339>.