[rt-users] second-level sort

[Ben Goodwin]

Yes, this is due to the addition of a 'UNIQUE' in the SELECT call in the
more recent DBI::Searchbuilder's.  The resulting MySQL query returns data in
a different order - if you can even call it an order.
My solution was to use the newer "OrderByCols" feature.  I copied
share/Elements/MyTickets to local/html and replaced the following line at
the bottom:

$MyTickets->OrderBy(FIELD => 'Priority', ORDER => 'DESC');

With

$MyTickets->OrderByCols((FIELD => 'Priority', ORDER => 'DESC'), (FIELD =>
'id', ORDER => 'ASC'));

This seems to bring it back into line with previous behavior.
You'd need to do the same with MyRequests and any other elements that
generate a listing.

	-=| Ben


-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Adam Hirsch
Sent: Thursday, March 04, 2004 9:23 AM
To: 'RT users'
Subject: Re: [rt-users] second-level sort

Mike Husband (m.husband at leadup.com.au) wrote:

> I think the default sort order is by ticket priority,
> but if you select any queue you can choose the sort order
> by clicking on headers

Right, the issue is when one has it sorted by owner, and want to see the
tickets owned by a given person in chronological order... make sense?

i.e. if I've got the queue grouped by owner, and I'm looking at regis'
tickets, they're in some weird, nondeterministic order:

[snip]

in RT2, they'd be grouped by owner, but then in numeric ticket order within
each person's tickets.

Anyone else seen this?

Adam

-- 
Schmendiman: Remember, the shortest distance between two points is a foot
and
             a half.  No pun intended.
     Freddy: No pun achieved.
     - Steve Martin, _Picasso at the Lapin Agile_
<adam at baz.org>
_______________________________________________
rt-users mailing list
rt-users at lists.bestpractical.com
http://lists.bestpractical.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm