Bug 8462 - Implement sorting on build status page
: Implement sorting on build status page
Status: VERIFIED FIXINBUILD
Product: sourcejuicer
general
: unspecified
: ANY/Generic All
: P2 normal
: ---
Assigned To: os-tools
: os-tools
:
:
:
:
: 8690
  Show dependency treegraph
 
Reported: 2009-04-27 06:52 UTC by Brian Nitz
Modified: 2009-05-20 07:46 UTC (History)
1 user (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Brian Nitz 2009-04-27 06:52:22 UTC
I'm keeping this bug open to track the need for sorting, pagination and
grouping to work together on build status and eventually myjucr pages.

I implemented and committed the paginated sort fixes on the review page (bug
7933) on Friday, but I didn't commit the changes which enable sort on the build
status page because the sorting of paginated and grouped jobs results in
grouping which isn't intuitive.  (For example, if there are 5 pages, but only
1.5 pages of 'current jobs', sorting in an order which puts current jobs at the
back results in a page one which makes it appear as though there aren't any
current jobs.  

I'm not sure what is the best answer here and the implementation is complicated
by the fact that sliced (paged) query sets can't be sorted and the fact that
some of the fields we'd want to sort are attributes of children or
grandchildren of jobs rather than attributes of the job.
Comment 1 Brian Nitz 2009-05-05 03:15:01 UTC
Fix committed
Comment 2 Kevin McAreavey 2009-05-08 02:55:22 UTC
Builds are being re-sorted by status every time you navigate to Build page,
e.g.

Submit some builds
Navigate to build page
Select Build tab multiple times

The table is reverse ordered by Status as it would when selecting the Status
column title, this is particularly confusing if the builds are paginated.
Comment 3 Brian Nitz 2009-05-15 09:02:15 UTC
Fix committed