lp email 'rationale' header should use most specific criterion, or add header for direct subscription

[Chad Miller]

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-Bug-Commenters' email header. Great.

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-Message-Rationale: Subscriber @big-group-name',

I would rather have 'X-Launchpad-Message-Rationale: Subscriber bug#12345' (since that is more specific than group membership and group-subscription of a project), or some other header that indicates that I am a subscriber to a specific bug.

[Martin Packman (gz)]

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?

[Selene ToyKeeper (toykeeper)]

I have noticed this too. I have to do something beyond subscribing to a bug in order to make it filterable.

Attached is a file with two notifications I received and the diff between them. In the first message, I was subscribed only through a group. In the second message, I was subscribed directly (I subscribed then had someone else update it to generate a new notification). In both cases, the relevant headers and footer are identical.

It would be really nice to have some sort of indication that I've shown a direct interest in a bug without having to add a comment or assign it to myself... one way to do this would be to simply omit the team name if I'm subscribed directly, or to include the bug number in the rationale as suggested above.