When commenting, I'm invited to subscribe to a bug I'm already implicitly subscribed to.

[Steve Alexander]

When I comment on a bug that I'm already implicitly subscribed to (via a bug contact), I see this:

 [ ] E-mail me about changes to this bug report

If I'm already getting emailed about changes to this bug report, this checkbox should be checked already.

In this case, unchecking the checkbox would unsubscribe me from this bug.

An alternative fix is to not display the checkbox and text when I'm already implicitly subscribed.

[Brad Bollenbach (bradb)]

I too have noticed it's strange and misleading to see the "E-mail me..." checkbox when I'm already getting bugmail by way of team membership for a bug.

mpt, should this checkbox be checked already if you're already getting bugmail via team membership or indirect subscription? Should it not be shown at all in that case? Is there an even better approach, that is a step between where we are now and the portlet-based subscription UI?

[Björn Tillenius (bjornt)]

On Wed, Aug 30, 2006 at 03:00:40PM -0000, Brad Bollenbach wrote:
> I too have noticed it's strange and misleading to see the "E-mail me..."
> checkbox when I'm already getting bugmail by way of team membership for
> a bug.

Steve, was this what the bug report was about? From reading it, it's
not clear whether you were subscribed directly or via a team. (i.e.
whether there was a bug in the 'display checkbox' logic, that has since
been fixed)

> mpt, should this checkbox be checked already if you're already getting
> bugmail via team membership or indirect subscription? Should it not be
> shown at all in that case? Is there an even better approach, that is a
> step between where we are now and the portlet-based subscription UI?

FWIW, I subscribe to bugs all the time, even though I get bug mail via
launchpad-bugs. It's a way for me to keep a more track of certain bugs
more closely. The wording 'Email me...' is a bit strange, though, maybe
we should reword it to talk about subscriptions instead?

[Matthew Paul Thomas (mpt)]

Subscription is the process of signing up to something to receive updates, episodes, etc. So changing "e-mail me" to "Subscribe me" here would be making it a bit more abstract without really changing the meaning. And I think "I'm invited to subscribe to a bug I'm already subscribed to" is pretty good evidence that switching to "subscribe" terminology wouldn't make this problem any better.

I agree that the checkbox should be checked if you receive e-mail about the bug for any reason that Launchpad knows about. (This will gradually become any reason at all, as things like project subscriptions replace things like the launchpad-bugs@ mailing list.) And the checkbox should also be disabled if Launchpad is currently unable to unsubscribe you individually. (Which should gradually become never.)

[Brad Bollenbach (bradb)]

On 31-Aug-06, at 1:08 AM, Matthew Paul Thomas wrote:

[snip]

> I agree that the checkbox should be checked if you receive e-mail
> about
> the bug for any reason that Launchpad knows about. (This will
> gradually
> become any reason at all, as things like project subscriptions replace
> things like the launchpad-bugs@ mailing list.) And the checkbox should
> also be disabled if Launchpad is currently unable to unsubscribe you
> individually. (Which should gradually become never.)

Does this apply to the action menu too? Should the Subscribe/
Unsubscribe menu option read only "Unsubscribe" if one of your teams
is currently subscribed to this bug but you aren't?

[Matthew Paul Thomas (mpt)]

I think there isn't really any good answer to that question, because the action menu shouldn't exist. However, while the menu does exist, I think the "Subscribe/Unsubscribe" item is better with its current logic than it would be with any other logic.

[Christian Reis (kiko)]

I would like to second Bjorn's statement that, even though I do get email via the launchpad-bugs list, I choose to subscribe to specific bugs that I am interested in, and I filter that differently. It would be ideal if when resolving this confusion we didn't lose that ability.

[era (era)]

This "feature" is valuable because it allows you to explicitly subscribe to a bug for which you have reported a duplicate bug. In this "pseudo-subscribed" mode, neither the original bug nor the one it's a duplicate of shows up in searches (this is bug #61429 ... it would be ideal if that could be fixed first, of course).

[era (era)]

What's with the "Needs Info" tag on this one, is that still topical?

[Christian Reis (kiko)]

Because mailing lists can be used as contact addresses for teams, it is actually impossible to determine exactly whether or not you are being "Also Notified".

[Christian Reis (kiko)]

Maybe it is something in the wording, because "Also Notified" is not the same as a "Subscription". But we'd need to make that clearer.

[Michael Rooney (mrooney)]

Okay so no one has mentioned this in a while but the issue does seem to still exist, and is a little confusing. I have to think "wait, am I already subscribed to this?" every time I see it. It would be nice to not show up if I am already implicitly subscribed. Any recent thoughts on this?

[Paul Sladen (sladen)]

I just ended up filing a dup of this...

Perhaps we could either have the tickbox turned into radio buttons (hard) or simply reword so that it is context aware:

  [ ] Subscribe personally to this bug report (in addition to notification received: xxx-membership and duplicate bug #1234).

[Graham Binns (gmb)]

Now that the comment form is AJAXified I don't think this is a problem any more. I'll mark it invalid and we can reopen it if I'm wrong.