fine-tune delivery of duplicate notification mails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Björn Tillenius |
Bug Description
I have a few bugs that are extremely heavily duplicated (bug 41865, bug 41921, bug 43012, etc.). Recently I've begun getting a few complaints from people who reported various of the duplicates that ever since they filed their bug they've been deluged by mail; this seems to be because they get a notification every time another duplicate is added.
Now, the duplicate notification is very useful to those who care directly about the original bug, particularly the responsible developer; without the notification it is not always possible to tell when somebody has marked another bug as a duplicate of one you care about (they might not sync up the status), and I often rely on this to be able to correct mistaken duplications. So, I'm certainly not asking for the duplicate notifications to be disabled.
However, it occurs to me that it might not be terribly useful to deliver duplicate notifications to people only subscribed via dupes and not subscribed directly to the target bug. My hypothesis is that the people who most care about the duplicate notifications are subscribed to the master bug anyway, by virtue of e.g. being the responsible developer. If this is true, then it could make sense to deliver duplicate notifications only to people subscribed directly to the target bug, but not to those subscribed to some other duplicate of the target bug.
The relative information content of "somebody else reported the same bug you did" and "we have a question about your bug" suggests intuitively to me that this might be the right place to put a boundary.
Changed in malone: | |
milestone: | 2.2.6 → 2.2.7 |
Changed in malone: | |
assignee: | nobody → Björn Tillenius (bjornt) |
status: | Triaged → In Progress |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Thanks for your bug report.
I'm not yet sure how best to address the underlying issues here, but your proposal sounds like a potential solution.