Bug mail should use my verbose_bugnotifications, not the team's

Bug #253788 reported by William Grant on 2008-07-31
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Medium
William Grant

Bug Description

Bug notifications that get to me because I'm a member of a team don't respect my verbose_bugnotifications setting. It seems to use the team's instead.

Note that this come directly to me (not via a team mailing list), so it is fixable.

Related branches

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

2008/7/31 William Grant :
> Public bug reported:
>
> Bug notifications that get to me because I'm a member of a team don't
> respect my verbose_bugnotifications setting. It seems to use the team's
> instead.
>
> Note that this come directly to me (not via a team mailing list), so it
> is fixable.
>

Can you provide details of a bug on which this happened and the
headers of one of the offending emails?

 status incomplete

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFIkjcAwutMq02tGPoRAnZdAJ0d2cxI452s2JW20jHzGVzVv5WuqwCghP1Y
F2zCvrkN4++tm92UvmWEwPE=
=1ica
-----END PGP SIGNATURE-----

Changed in malone:
status: New → Incomplete
William Grant (wgrant) wrote :

Here's one from one of my teams. All email for teams is like this, while non-team mail has the extra information in the signature.

Changed in malone:
status: Incomplete → New

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

2008/7/31 William Grant :
> Here's one from one of my teams. All email for teams is like this, while
> non-team mail has the extra information in the signature.
>
> ** Attachment added: "example of a team email"
> http://launchpadlibrarian.net/16460213/swatmail
>
> ** Changed in: malone
> Status: Incomplete => New
>
> --
> Bug mail should use my verbose_bugnotifications, not the team's
> https://bugs.launchpad.net/bugs/253788
> You received this bug notification because you are subscribed to
> Launchpad Bugs.
>

Right, thanks.

 status triaged

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFIksjHwutMq02tGPoRAsgDAJ9frFTaImE6pnfGn7815MgCUH/PpACfR3ef
K4iQVJi745VXbGd1x9SN86A=
=+dbR
-----END PGP SIGNATURE-----

Changed in malone:
status: New → Triaged
Martin Pool (mbp) wrote :

There doesn't seem to be any UI to turn off verbose_bugnotifications for a team. Can it be done in the db?

Diogo Matsubara (matsubara) wrote :

I think we should either enable the UI for teams or at the moment a bug notification is generated check the team members verbose_bugnotification settings and act accordingly. The latter sounds expensive. I'll ask Graham to comment here.

Martin Pool (mbp) wrote :

See also <https://bugs.edge.launchpad.net/malone/+bug/251501> pointing out this is particularly silly when it causes the exact same lengthy text to be included twice.

I filed https://answers.edge.launchpad.net/malone/+question/76825 asking for this to be turned off at least for our teams, pending a fix to this bug, if that can be easily done.

Graham Binns (gmb) on 2009-07-15
Changed in malone:
importance: Undecided → Medium
Steve McInerney (spm) wrote :

gmb, can you advise if it's safe, or even effective?, to just toggle this in the DB (person table aiui)?

per poolie's request: https://answers.edge.launchpad.net/malone/+question/76825

On Thu, Jul 16, 2009 at 12:11:45AM -0000, Steve McInerney wrote:
> gmb, can you advise if it's safe, or even effective?, to just toggle
> this in the DB (person table aiui)?

Yes, that's perfectly safe. I'm assuming it will be effective, but even
if not it won't do any damage.

William Grant (wgrant) on 2009-07-23
Changed in malone:
assignee: nobody → William Grant (wgrant)
status: Triaged → In Progress

Fixed in devel r8976.

Changed in malone:
status: In Progress → Fix Committed
Changed in malone:
milestone: none → 2.2.8
William Grant (wgrant) on 2009-11-06
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers