In patches view, offer sorting on patch age.
Bug #512500 reported by
Karl Fogel
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Karl Fogel | ||
Bug Description
In any "+patches" view, we should offer sorting by patch age. This is tricky, because large result sets will be batched for pagination, and we don't want to do a simple javascript sort on the patches in the current page, but rather sort across the entire result set (regenerating the current page if necessary). Abel had some ideas about how to do this in an SQL query.
Note: this is deferred from bug #506018 (which is about implementing the patches view in general).
| Changed in malone: | |
| assignee: | nobody → Karl Fogel (kfogel) |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Karl Fogel (kfogel) wrote | #1 |
Revision history for this message
| Diogo Matsubara (matsubara) wrote Bug fixed by a commit | #2 |
| Changed in malone: | |
| status: | Triaged → Fix Committed |
| Changed in malone: | |
| milestone: | none → 10.02 |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
And just in case there was any doubt:
<kfogel> bryce: how important is it to be able to sort by patch age?
(see https:/
<bryce> kfogel, I'd say it would be pretty important
<kfogel> bryce: *nod* I'm not surprised, and abel and I have it on
our list. But I wanted to confirm, because we could save a
lot of time if we didn't have to do it :-).
<kfogel> no problem
<bryce> kfogel, I'd say it's a pretty key feature.
<kfogel> bryce: I'll note it in the bug.