When a bug is marked as duplicate, you are invited to subscribe to the master bug
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Graham Binns | ||
Bug Description
If one of the bugs you report is marked as duplicate, you receive a mail like this:
*** This bug is a duplicate of bug XXXX ***
https:/
** This bug has been marked a duplicate of bug XXXX
bzr push reporting AssertionError on terminal
* You can subscribe to bug XXXX by following this link: https:/
The last sentence (you can subscribe...) is useless because you are automatically subscribed to the master bug and also to all the duplicates. Putting this sentence makes the e-mail longer and also tells the user to spend time doing a step that is not necessary. But the most important problem is that, following the link to the +subscribe page, the only option you are given is to *unsubscribe* from the bug.
Related branches
- Graham Binns (community): Approve
-
Diff: 164 lines (+31/-63)4 files modifiedlib/lp/bugs/adapters/bugchange.py (+4/-20)
lib/lp/bugs/doc/bug-change.txt (+0/-1)
lib/lp/bugs/doc/bugnotification-sending.txt (+16/-2)
lib/lp/bugs/tests/test_bugchanges.py (+11/-40)
| Graham Binns (gmb) wrote | #1 |
| tags: | added: story-better-bug-notification |
| affects: | launchpad → malone |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| status: | Triaged → In Progress |
| Robert Collins (lifeless) wrote | #2 |
| Changed in launchpad: | |
| importance: | Medium → High |
| status: | In Progress → Triaged |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Graham Binns (gmb) |
| Launchpad QA Bot (lpqabot) wrote | #3 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
I'm un-marking this as a duplicate given some discussions on the other bug. There are twp possible solutions to this problem:
1. Don't keep notifying the subscribers of duplicate bugs about changes to the master.
2. Drop the link altogether.