+affectingbugs does not list bugs where a duplicate affects the user
Bug #343110 reported by
Sense Egbert Hofstede
This bug affects 24 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When you've let Launchpad know that bug X affects you and someone marks bug X as a duplicate of bug Y, bug Y doesn't affect you.
All people affected by bug X should also automatically be treated as affected by bug Y.
See also bug 678090 which is about the narrower thing that the count of affected users shown on the bug ought to be the sum of affected users across all dupes. Beyond that:
* sorting by number of affected users ought to be the number including dupes
* https:/
Changed in malone: | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: bug-page confusing-ui story-bug-heat |
description: | updated |
tags: | added: affectsmetoo |
summary: |
- UI: When the bug that affects you is a duplicate the master doesn't - affect you + +affectingbugs does not list bugs where a duplicate affects the user |
tags: | added: bug-search |
To post a comment you must log in.
Dear friends,
I agree with this behavior.
What happens when bug X is then mis-marked as a duplicate of bug Y?
I think that in this case bug Y should be marked as "doesn't affect me" if it was previously marked as "affects me" automatically. However, if bug Y was "affects me" before bug X became a duplicate of it, it should remain that way.
Many blessings.