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

Reported by Sebastien Bacher on 2005-05-03
168
This bug affects 19 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Yellow Squad

Bug Description

Malone should have an option to not send emails about bug changes to the person doing the change.

Related branches

lp:~gary/launchpad/bug548-db-2
Merged into lp:launchpad/db-devel at revision 10177
Gavin Panella: Approve on 2011-02-03
Stuart Bishop: Approve (db) on 2011-02-03
Robert Collins: Pending (db) requested 2011-02-02
lp:~gary/launchpad/bug548
Merged into lp:launchpad at revision 12339
Graham Binns: Approve (code) on 2011-02-08
Brad Bollenbach (bradb) on 2005-11-02
Changed in malone:
assignee: nobody → bradb
status: New → Accepted
Brad Bollenbach (bradb) on 2006-08-18
Changed in malone:
assignee: bradb → nobody
Christian Reis (kiko) on 2006-09-23
description: updated
dresnu (dresnu) wrote :

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.

Matthew Nuzum (newz) wrote :

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. :-(

Matt Zimmerman (mdz) wrote :

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;
}

Mark (mark-wege) 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.

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.

flrtx (fltrx) on 2009-09-25
description: updated
summary: - don't send mails about changes to the people doing the change
+ Launchpad sends notifications updates to the members that change
+ reports.
summary: - Launchpad sends notifications updates to the members that change
- reports.
+ Launchpad sends notification updates to the members that change reports.
Matt Zimmerman (mdz) on 2010-01-12
summary: - Launchpad sends notification updates to the members that change reports.
+ Launchpad sends change notification updates to the person who requested
+ the change
Graham Binns (gmb) on 2010-06-04
tags: added: story-better-bug-notification
Graham Binns (gmb) on 2010-06-04
Changed in malone:
importance: Medium → High
Brian Murray (brian-murray) wrote :

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.

Graham Binns (gmb) on 2010-08-11
tags: added: story-better-notification-sending
Martin Ueding (martin-ueding) 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.

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

Brad Crittenden (bac) wrote :

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

Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Launchpad Yellow Squad (yellow)
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.02
Ian Booth (wallyworld) on 2011-02-07
tags: added: qa-ok
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
Gary Poster (gary) on 2011-02-10
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui) on 2011-02-11
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers