The Queue page is "next to useless" in our case. For example currently there are over a 1000 simultaneous builds running. With a hardcoded pagination of 25 navigating to a specific area of the queue is almost impossible - by the time you have figured which page it might be in, the queue has already "lived" enough for it to be something completely different. Each click also takes tens of seconds to load.

While there is probably a good reason that the page is that slow (although any performance improvements would be welcome), a few simple ideas would make the page more usable:
-Possibility to filter items in the queue by the columns that it's possible to sort them by - for example "Only show builds that are of config xxx/yy"
-Possibility to tune the pagination value - 25 is just too low
-grouping builds with hide/expand functionality by parent/child relationship --thus being able to show more per page - when collaped it could just show a number "20 builds currently running in this tree"
-grouping builds with triggered/triggeree relationship - thus being able to show more per page
-Link to node running the build being displayed