Default sort order is braindead broken in User and Project lists

[David Medberry]

The default returned search order in the Admin panel for Users and Projects return them in "id" order, not name order. The ID order is, by design, opaque and useless so it is tantamount to idiocy to use that as the default sort order. (It's like saying, "Return things in random order on purpose", said with a diabolical peel of laughter....)

Ie, the "admin" user (typically the first user created) appears on the third page, when either sorting by date created (which likely isn't available) or alphabetically would put it much much much higher up the list.

This is another UX bug.

[Eric Peterson (ericpeterson-l)]

the way it works is that each service lists the items according to the api call, and they might limit the number returned to the page count + 1. In order to get this really implemented, each service would need to support a sort by query param.

In addition, each time the column sort gets clicked, we might need another server api call..... etc. This is going to reach into many areas.

[Gary W. Smith (gary-w-smith)]

Moving to wishlist since it cannot be addressed without corresponding changes outside of horizon.