Using "Also affects" (adding a bugtask) isn't shown in bug page activity
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
1. At <https:/
2. Use one of the "Also affects" links to mark the bug as also affecting anything else, e.g. (thanks to bug 80902) the lifesaver package in Ubuntu.
3. Change the bug's status in the Lifesaver project from "New" to "Invalid".
4. Reload the page (which you shouldn't need to do, but that's a separate bug).
What you should see:
* The bug description.
* "You marked this bug as affecting Ubuntu’s lifesaver package."
* "You changed the status in Lifesaver from New to Invalid."
What you actually see:
* The bug description.
* "{Your Name Here} 7 seconds ago / Changed in lifesaver: /status: New → Confirmed"
* No mention of the "Also affects" at all.
This bug contributed, in a small way, to the rage in bug 557177.
This is the sequel to bug 95732: the +activity page does show the databasese "bug task added", but most people will never see that.
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
I was disappointed to see how our bugs contributed to people being upset in bug 557177. And we definitely need to fix this.
However, we have a number of little (i.e. not difficult) bugs like this that we're having to work our way through. So I don't see this one being fixed inside the next 3 months, and for that reason I am marking it low priority. But "low" is certainly not accurate based on the trouble this issue caused recently.
Cheers,
deryck