Closed Bug 274766 Opened 20 years ago Closed 19 years ago

Default Sort Changed

Categories

(Bugzilla :: Query/Bug List, defect)

x86
Other
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: david, Assigned: justdave)

References

Details

With the prior version of Bugzilla, the default sort for bug lists was by ID
number.  Now it is by Severity.  This change is not on the lists of "New
Features" or "Bug Fixes".
Oops!  The default seems to be by Status, not Severity.  It's still different
from Bug ID, which was the previous default.  
David: I deleted my LASTORDER cookie and went to
https://bugzilla.mozilla.org/query.cgi?format=advanced
The dropdown contained the four options "Bug Number", "Importance", "Assignee"
and "Last Changed", and "Bug Number" was selected.

Can you be more specific? Where does your "Status" ordering come from? What
happens when you delete the LASTORDER cookie and revisit the search page?

Gerv
My cookies.txt file is "locked" as read-only.  It contains no
bugzilla.mozilla.org cookies.  

The problem appears when I request a stored query that I previously created. 
The last time I updated that query (after I first noticed this problem), I
explicitly requested "Bug Number" for Sort results by:.  

When I now request that query, I do get a LASTORDER cookie with the value
"bugs.bug_status%2C%20bugs.priority%2C%20map_assigned_to.login_name%2C%20bugs.bug_id",
which translates to 
"bugs.bug_status, bugs.priority, map_assigned_to.login_name, bugs.bug_id". 
Although this cookie has an expiration of "Thursday, December 31, 2037 4:00:22
PM", it would not survive my terminating Mozilla.  

As requested, I removed cookie LASTORDER and re-requested my stored query.  The
sort was again by STATUS.  I then selected ID to re-sort by Bug number.  The
LASTORDER cookie reappeared, this time with the value "bugs.bug_id".  I again
removed cookie LASTORDER and again re-requested my stored query.  The sort was
again by STATUS.  

Please note that I have always marked cookies.txt as read-only unless I
specifically know I want to store a set of cookies.  If I do want to store one,
I terminate Mozilla, change the cookie to read-write, visit only the Web site
from which I want the cookies, terminate Mozilla, and finally return the file to
read-only.  This way, I can navigate sites that insist on setting cookies (saved
non-session cookies, not merely session cookies) without them being actually
saved.  It would be nice if Mozilla had an option to treat non-session as if
they were session cookies.  
David: Could you paste the URL for the stored query here?

> If I do want to store one,
> I terminate Mozilla, change the cookie to read-write, visit only the Web site
> from which I want the cookies, terminate Mozilla, and finally return the file to
> read-only.

Wow... I wish I had as much spare time as you. ;-)

Gerv
(In reply to comment #4)
> David: Could you paste the URL for the stored query here?

That won't help anything except give us the name of the query.  But I'd be happy
with that, since this is on bugzilla.mozilla.org, I can pull it from the
database myself if I know the name of it.

The sort order is saved with your search when you save a search, if you have
anything other than "reuse same sort as last time" selected on the query page
when you create it, or if you change the sort order around using the column
header links before saving it.  I suspect the order you're getting was saved
with the query.

None of the "named" sort orders currently uses the sort order you got, so it's
unlikely that a possible change in definition of one of the named sort orders
would have been the culprit.

The current definitions, for reference:

Bug Number = "bugs.bug_id";

Importance = "bugs.priority, bugs.bug_severity";

Assignee = "map_assigned_to.login_name, bugs.bug_status, bugs.priority,
            bugs.bug_id";

Last Changed = "bugs.delta_ts, bugs.bug_status, bugs.priority,
                map_assigned_to.login_name, bugs.bug_id";
The query URL is
<https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=mylist>. 
This runs under my user ID <david@rossde.com>.  

Note:  As a workaround, I allowed cookie LASTORDER to be written to my
cookies.txt file.  And yes, that required some effort.   
Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.
Assignee: justdave → query-and-buglist
QA Contact: mattyt-bugzilla → default-qa
oops, this should still be mine.
Assignee: query-and-buglist → justdave
Many apologies for the multi-month delay, this accidently got nailed by a
mass-reassign, and didn't get caught, so it dropped off my radar.

Your 'mylist' query does *not* contain a saved sort order.  We've also had a
Bugzilla upgrade since this was last touched, it's possible the upgrade may have
cleaned that up.  Can you check and see if this is still happening?
This is still a problem.  Sort-order is apparently not saved within a query. 
It's set via a cookie.  The default used to be sorting by bug ID number.  That
is no longer the default sort order.  

To test this, use the Cookie Manager to delete all bugzilla.mozilla.org cookies.
 Then execute my query.  

I have a work-around:  I unlocked my cookies file to "read-write".  After
getting the query sorted the way I want it, I deleted the bugzilla.mozilla.org
cookies except for LASTORDER.  I then exited Mozilla and relocked the cookies to
"read-only".  

Did some digging in bonsai...  the default sort order has been "status,
priority, assignee, bug_id" since Bugzilla was ported to Perl in 1998, and has
never changed, except for the names of the columns in the database which
provided those fields.  If you had it sorting by bug_id, you must have had a
cookie saved that said that, or had order=bugs.bug_id or order=Bug%20Number in
the URL you were using to access the query.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.