Launchpad itself

Showing subscribers to duplicates under "May be notified" is confusing

Bug #2021971 reported by Nathan Teodosio
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Let's say bug D is marked duplicated of bug B.

I see that there is a handful of "subscribed to all changes" users in D, but they are listed under "may be notified" in B.

Wouldn't it make more sense to subscribe all subscribers to D to the corresponding category of B?

Revision history for this message
Colin Watson (cjwatson) wrote :

They're treated as indirect subscribers; copying the subscriptions over to the duplicate target would mean that if it turned out that somebody had made a mistake in setting the duplicate target then it would be hard to undo that.

I believe that subscribers from duplicates are still notified about changes - have you observed otherwise? Is this just about the way they're displayed in the UI?

Revision history for this message
Nathan Teodosio (nteodosio) wrote : Re: [Bug 2021971] Re: Carry over subscriber status to the duplicate target

> They're treated as indirect subscribers;

That means that they are actually notified as they normally would for
both bugs, as long as the duplicate status stands?

> copying the subscriptions over
> to the duplicate target would mean that if it turned out that somebody
> had made a mistake in setting the duplicate target then it would be hard
> to undo that.

True, makes sense.

> I believe that subscribers from duplicates are still notified about
> changes - have you observed otherwise? Is this just about the way
> they're displayed in the UI?

I wasn't able to observe the effect myself.

The UI led me to believe that they possibly wouldn't be notified, as
they are then under "may be notified" (which is not very clear of
itself, I assume that category is for users under more specific
notification rules, but that's another topic).

Guruprasad (lgp171188)
tags: added: lp-bugs
Changed in launchpad:
status: New → Incomplete
Revision history for this message
Colin Watson (cjwatson) wrote :

They are actually notified, yes. I suspect that it might be this way due to performance issues with accurately working out the subscribers when rendering the bug page (though I haven't positively confirmed that - it might require some trawling through history), but I agree it's still confusing UI.

summary: - Carry over subscriber status to the duplicate target
+ Showing subscribers to duplicates under "May be notified" is confusing
tags: added: confusing-ui
Changed in launchpad:
status: Incomplete → Triaged
importance: Undecided → Low
Guruprasad (lgp171188)
summary: - Showing subscribers to duplicates under "May be notified" is confusing
+ 'may be notified' is ambiguous about whether the subscribers of
+ duplicates will be notified of a bug's changes
summary: - 'may be notified' is ambiguous about whether the subscribers of
- duplicates will be notified of a bug's changes
+ Showing subscribers to duplicates under "May be notified" is confusing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.