Package bug with low heat has 4 flames on its bug page
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Deryck Hodge |
Bug Description
This will make sense if you look at bug 505433. The bug has heat 14 and 4 flames, but it's because it is the only bug for the package. So this makes sense on one hand, but if you click through from a distribution bugs page where it has no flames, it's not obvious why there are suddenly all the flames.
bdmurray, james_w, and I discussed this on IRC and some options came to mind:
* Always use the distribution as max_bug_heat source for the bug page
* Always use the package as the max_bug_heat source, even in distro bugs listings
* Use some scale between the distro flames and the package's bug list
The latter is an interesting idea, but doesn't solve the issue of the distro bugs list having one set of flames and the bug page another.
I lean on the side of the first option, but I'm open to discussion of these ideas and proposal of others.
Related branches
- Eleanor Berger (community): Approve (code)
-
Diff: 55 lines (+34/-2)2 files modifiedlib/lp/bugs/browser/bugtask.py (+5/-1)
lib/lp/bugs/stories/bugs/xx-bug-heat-on-bug-page.txt (+29/-1)
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: story-bug-heat |
Changed in malone: | |
status: | Triaged → In Progress |
assignee: | nobody → Deryck Hodge (deryck) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in malone: | |
status: | Fix Committed → Fix Released |
mpt pointed out another manifestation of this bug. See the tag list:
https:/ /edge.launchpad .net/ubuntu/ +bugs?field. tag=metadata
Several bugs at the bottom look like the same bug, but one has four flames. It is the only bug in it's package again.
So apparently we do use the package context in a list of Ubuntu bugs. I'm not sure that's right. If we need to file a new bug about that, I can.