User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:22.214.171.124) Gecko/2008120122 Firefox/3.0.5
I normally like to sort first by prio, then by sev, then by component, and finally by summary. So I just click those column headings in the reverse order. This prepends the following to my LASTORDER cookie in 3.0.3:
In 3.2, after clicking the column headings for summary, component, and severity, my LASTORDER cookie starts with:
If I then click the priority heading, the severity sort key gets lost:
Initially reported in bug 164009 comment 16.
I can confirm this happening in current trunk verison. There's some funky things going on with the order parameter when there's multiple order columns. Same funkiness can be seen on the URL order param, which then gets stored in LASTORDER cookie.
I have a feeling that this might get fixed by the patch in bug 164009 but we'll see.
This is caused by a regression introduced by 23473 since it eagerly modifies the global order variable when using order.remove() to remove duplicate columns. This then affects rest of the columns after the first column from the current sort order.
As I suspected this is fixed by the latest patch in bug 164009.
(In reply to comment #2)
> As I suspected this is fixed by the latest patch in bug 164009.
The relevant part of this patch, which I suppose is the regexp, has been fixed separately in bug 510944, so I'm pretty sure this is now fixed in Bugzilla 3.4.2.
This is still not working in 3.4.4+, but is fixed on trunk. I don't have permission to change the target milestone, and I'm not sure whether this warrants a reopen for further work on the 3.4 branch, so I'll let others decide how to handle it.
Running the query https://landfill.bugzilla.org/bugzilla-3.4-branch/buglist.cgi?query_format=advanced&bug_status=ASSIGNED&product=FoodReplicator and using http://addneditcookies.mozdev.org/ to look at my cookies, I see:
2. click the "summary" header
4. click the "comp" header
6. click the "sev" header
8. click the "pri" header
On https://landfill.bugzilla.org/bugzilla-tip, I instead see:
> (In reply to comment #2)
> The relevant part of this patch, which I suppose is the regexp, has been fixed
> separately in bug 510944, so I'm pretty sure this is now fixed in Bugzilla
Please reopen this bug as it is definitely not fixed in Bugzilla 3.4.4+ (also see comment 4). Comparing the order parameter in the URL on four different Bugzilla versions after clicking Pri, Sev, Assignee:
Bugzilla 3.0.10+ (https://landfill.bugzilla.org/bugzilla-3.0-branch/):
Bugzilla 3.2.5+ (https://landfill.bugzilla.org/bugzilla-3.2-branch/):
Bugzilla 3.4.4+ (https://landfill.bugzilla.org/bugzilla-3.4-branch/):
Bugzilla 3.5.2+ (https://landfill.bugzilla.org/bugzilla-tip/)
OK, you're right; this bug is not fixed on the 3.4 branch. 3.5.2 is not affected thanks to bug 164009. I have a patch for 3.4.5.
Created attachment 423381 [details] [diff] [review]
We must not replace $order by its trimmed value. This patch is similar to what has been done upstream. wicked: this patch is for the 3.4 branch only, see my previous comment.
Committing to: bzr+ssh://email@example.com/bugzilla/3.4/
Committed revision 6719.