"Package bugs" page has no indication of how numbers have changed
Bug #284400 reported by
Matthew Paul Thomas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Colin Watson in <https:/
"No matter what the size, though, I find that the thing I really miss from +packagebugs is some indicator of the rate of change. A package with 100 bugs but no new ones for the last year is much less interesting than a package with 20 bugs 15 of which were filed in the last week."
An example of the page in question: <https:/
One way of fixing this would be to have a short sparkline of the past month's values to the left of each bug count.
A nice example of sparklines in a data table: <http://
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: feature |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
To post a comment you must log in.
Another thing we could use is some function on heat in the packages - heat includes a decay function so many old bugs will have less heat than the same number of newer bugs. [assuming all the factors driving heat are equivalent]