lp email 'rationale' header should use most specific criterion, or add header for direct subscription
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
I'm a subscriber to a LP group that gets a lot of bugs. I wish to filter the ones that involve me in some way other than the group membership.
If I'm a commenter to a bug, I get the 'X-Launchpad-
If I'm assigned the bug, I get 'X-Launchpad-Bug: assignee=me'. Great.
If I subscribe to a bug directly that is in a group I'm subscribed to, I get no additional information about the subscription to that single bug. I do get a 'X-Launchpad-
I would rather have 'X-Launchpad-
affects: | launchpad → malone |
Changed in malone: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: story-better-bug-notification |
tags: | added: notifications |
tags: | added: email |
This specificity problem also goes for the note at the bottom of the email. My email client only supports filtering on a limited number of headers, so can't use X-Launchpad- Message- Rationale and need to use the message contents instead.
Having joined a few teams, I'm no longer getting the useful "You received this bug notification because you are a direct subscriber of the bug." for bugs I filed or manually subscribed to, but instead a firehose of "You received this bug notification because you are a member of $team, which is subscribed to $project." for everything.
A variation of this bug may also be present in email notifications for other things like merge proposals, but I've not yet received one to check. Would that need filing against another launchpad component?