In patches view, offer sorting on patch age.

Bug #512500 reported by Karl Fogel on 2010-01-25
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
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).

Karl Fogel (kfogel) on 2010-01-26
Changed in malone:
assignee: nobody → Karl Fogel (kfogel)
Curtis Hovey (sinzui) on 2010-01-26
Changed in malone:
status: New → Triaged
importance: Undecided → High
Karl Fogel (kfogel) wrote :

And just in case there was any doubt:

<kfogel> bryce: how important is it to be able to sort by patch age?

<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.

Changed in malone:
status: Triaged → Fix Committed
Deryck Hodge (deryck) on 2010-02-23
Changed in malone:
milestone: none → 10.02
Deryck Hodge (deryck) on 2010-03-12
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers