Roy, that's a good idea. We encountered the same thing, and we asked RWS Support to change the web interface so that non-admin users could view the entire queue -- not just their own jobs. IIRC, it was a pretty easy change for them to make. I know that's not exactly what you're asking for (you would like to display the queue in Pub Manager). But it might be useful as an interim fix.

Roy, that's a good idea. We encountered the same thing, and we asked RWS Support to change the web interface so that non-admin users could view the entire queue -- not just their own jobs. IIRC, it was a pretty easy change for them to make. I know that's not exactly what you're asking for (you would like to display the queue in Pub Manager). But it might be useful as an interim fix.

Agreed that the web client is the best place to enable this for now (and back when I was a customer using Tridion Docs, we did the same tweak). I do also take from Roy Janssen 's post the desirability of showing this more directly in publication management interfaces. Good input for future evolutions of the client tooling.

Good that it is recognized, I understand that giving access to the queue via the website is quite easy. However, this queue provides raw queue information that is not really suitable for an end user. For a user it is sufficient to know how much is in the queue, what is in the queue, and by whom is something in the queue. Publication manager is the primary tool a user works with, so it is the best place to implement it in the most user-friendly way possible. Perhaps this is functionality to include in the next release of Publication manager.

Regarding performance, in general, is my opinion; if a user experiences slowness, it is up to the application to provide insight into this. It makes quite a difference whether I make a PDF publication with 5000 topics or with 5 or if my publication is the 30th in the queue. Performance experience can therefore be influenced through communication in the application itself.