Yes please!
Creating more queues with less columns is not ideal, as I'm looking for a way to have all the essential details in one 'Overview' queue snapshot to quickly narrow down where there might be information gaps, SLAs not met, updates required etc.
We user JSM for client & end user support, so it's important for us to maintain the queue and escalate/prioritise/communicate on issues to best serve the customers, and having a 'one-view' snapshot to monitor quickly throughout the day would streamline that process by reducing the amount of clicks and time taken, along with reducing cognitive fatigue.
It would be amazing if the column width could be adjustable, or if columns could be collapsed/shown with one click, or if the padding could be reduced for a 'compact' view option.
—
Here are some links to the same/related questions in the Community:
https://community.atlassian.com/t5/Jira-Service-Management/Service-Desk-Queue-Columns-are-way-too-wide-all-of-the-sudden/qaq-p/949228 - 1197 views
https://community.atlassian.com/t5/Jira-Service-Management/how-to-change-the-size-of-the-columns-in-the-queues/qaq-p/1397703 - 487 views
https://community.atlassian.com/t5/Jira-Service-Management/column-width-JSD-queues/qaq-p/238039 - 531 views (actually wants to increase column width, but still speaks to the ability to control the width)
https://community.atlassian.com/t5/Jira-Service-Management/Is-it-possible-to-change-the-column-widths-in-a-queue/qaq-p/1333504 - 1261 views (same as above)
^Just based on the engagement of these community questions, there are more than three thousand of us looking for a solution!
There is also another issue that should possibly be linked: https://jira.atlassian.com/browse/JSDSERVER-6719

cffa6738037f That Atlassian builds their roadmap not according to what paying users ask for. I understand that some of these suggestions have issues based on how the page is coded. But saying nothing and just rotating them through the types or agents at Atlassian is annoying. We were sold snake oil in the fact that we were told what all Jira could do only to find out that it takes a paid for plug in to make that happen.