It should be possible to resort buglists without having to rerun the query. Jesse Ruderman's Greasemonkey script does just that. We should incorporate it into Bugzilla.

See also bug 151686, "sort buglist on the client rather than resubmit the query".

integrate's jesse's code, first cut. i didn't put a mozilla mpl boilerplate on the javascript file as i'm not sure what license jesse released his code under. this works but isn't ready for review, as it has the severity, status and resolution enums hardcoded (and it doesn't work on ie).

I plan to make the code open-source under a license that will allow it to be included in Bugzilla. I also plan to add some setTimeouts to make it not hang Firefox so badly as it sorts long lists.

BugSort is now MPL. See http://www.squarefree.com/2005/05/02/faster-bug-sort-user-script/. Some things that would probably have to be done for BugSort to be incorporated into Bugzilla: 1. Make sure it uses cross-browser DOM, etc. 2. Provide some way to change the default sorting method. This could be a "Use this sorting method for subsequent searches" button on resorted bug lists that changes the cookie, or it could be a dropdown in the userprefs page. 3. Provide a "URL for this resorted list" link. 4. Make it sort the date, target milestone, and version columns better. 5. Find a way to display sorting arrows (e.g. \u25B2 and \u25BC) without changing the column width.

I think i have a better script for this, just because it's easier to add. It's based on the kryogenix table sorting script. Look at it here: http://www.joostdevalk.nl/code/ it's very inobtrusive in that it only requires loading the script, and giving a table a class "sortable". It's MIT licensed, don't think we'd have a problem there. This might not do the fancy things your script does, but i think it does the trick.

We should be able to take care of sorting with one of the many ajax frameworks/toolkits. Here are examples of two approaches: http://archive.dojotoolkit.org/nightly/tests/widget/test_SortableTable.html http://openrico.org/rico/livegrid.page I think it would be best to use one of the existing frameworks so that we do not have to reinvent the wheel and so that there is not a fragmented base of these features. The only thing that would need work is connecting the JS framework to the cookie that remembers the sort field...

As neither bug has seen any activity, in the interest of having only one bug, I'm duping this bug to the older bug.