How to remove nested bug subscriptions?

Asked by Dimitri John Ledkov (ex-credativ) on 2011-11-25

1) User files a bug
2
) Developer requests feedback from accounting experts by subscribing the team to the bug
3
) My teams mailinglist ends up in the chain of the bug reports

Chain = Me -> Credativ Team -> OpenERP Accounting Experts -> Subscription on a bug

How can I make sure that indirect team bug subscriptions do not go to our team mailing list?

(Our team members subscribe to individual bugs already)

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
2011-12-05
Last reply:
2011-12-05
Benji York (benji) said : #1

It would help if I could see an example. Do you have any bugs in this state now?

These are the bugs that the team is actually subscribed to (count = 1):
https://bugs.launchpad.net/~credativ

Here is our bug mail flood:
https://lists.launchpad.net/credativ/

Pick any =)

You've got the mailing list set as the team's contact address which means that all email to the team goes there. You can just remove the contact address and people will be emailed individually instead for any emails that go the team.

How does that solve the problem? Cause then everyone will still be spammed with bug subscription, and still will have to click individually to unsubscribe.

Gavin Panella (allenap) said : #5

> How does that solve the problem? Cause then everyone will still be
> spammed with bug subscription, and still will have to click
> individually to unsubscribe.

When people receive bug mail via a mailing list, there is no way for
Launchpad to apply bug subscription rules because it treats the
mailing list as a single recipient.

Removing the contact address for the team means that Launchpad's bug
subscription rules come into play. Each member of the team must set up
a bug subscription for the projects that the OpenERP Accounting
Experts team touches, which is suboptimal, but it does give you a lot
more control.

For example, for OpenERP Server:

  1. Go to https://launchpad.net/openobject-server

  2. Click "Subscribe to bug mail"

  3. Fill in the details.

  4. Click the green tick icon to save.

If you want no mail at all there is a workaround (individual bugs can
be muted, but I don't think whole projects can):

  1. As above.

  2. As above.

  3. Fill in the details:

     - Bug mail recipient: Yourself
     - Subscription name: ... you choose ...
     - Receive mail for bugs affecting OpenERP Server that:
           are added or changed in any way

  4. Bugs must match this filter: Tags:

  5. Enter a random string for the tag.

  6. Click the green tick icon to save.

Another option might be to unsubscribe ~credativ from OpenERP
Accounting Experts and let the team members subscribe individually.

Gavin.

Can you help with this problem?

Provide an answer of your own, or ask Dimitri John Ledkov (ex-credativ) for more information if necessary.

To post a message you must log in.