people subscribed to bugs that are duplicates shouldn't receive notifications of new duplicates to the master bug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Medium
|
Unassigned |
Bug Description
This bug is a request for a change in launchpad email behavior.
The scenario is this:
1. User reports bug A, and is automatically subscribed to it.
2. Bug A is marked a duplicate of Bug B.
3. User is automatically subscribed to Bug B "from duplicates".
4. User receives notifications that 100 other bugs are duplicates of Bug B.
Oftentimes this means that an unassuming user now has a mailbox filled with duplicate notifications and doesn't really care to know how large of a problem their bug turned out to be. They just want to see discussion and status changes for the master bug, Bug B.
Therefore, I propose that when the above scenario occurs, users that are subscribed to Bug B "from duplicates" should receive all regular launchpad email notifications EXCEPT that other bugs are a duplicate of Bug B. This would eliminate the scenario of bug 86619 (Bug A) and bug 72018 (Bug B). Specifically, see https:/
Doing this would allow users to continue to see relevant discussion on large, duplicate prone bugs but not have an inbox overflowing with duplicate notifications. Not knowing anything about launchpad internals, I believe this is possible since the information of how users were subscribed to a bug is available (since the user is in the "From duplicates" column).
Please let me know if any other information is necessary.
Thanks
Changed in malone: | |
importance: | Undecided → Medium |
status: | Unconfirmed → Confirmed |