• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Queues
    • None
    • 30
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary:

      It would be nice to have the option to resize the queue columns on the new UI. Each component has its own size and when adding more columns a scrollbar shows up and we need to start scrolling in order to see all the columns.

      ps. If you are on edit view, the columns are laid out just fine.

       

          Form Name

            [JSDCLOUD-7842] Add the ability to resize queue columns

            Matt Russell added a comment -

            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.

            Matt Russell added a comment - 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.

            This UI complaint turned suggestion turned feature request is some 4-5+ years old and remains undelivered... what should one make of this I wonder?

            Benjamin Kelly-Taylor added a comment - This UI complaint turned suggestion turned feature request is some 4-5+ years old and remains undelivered... what should one make of this I wonder?

            Josh added a comment -

            We agree with many of the suggestions included in this thread:

            1. Ability to resize column width within queues just like it can be done in filters
            2. Give users the option to define whether column values wrap lines
            3. Allow users to expand / collapse columns

            The biggest pain point right now is column width, so hopefully that would be given priority.

            Josh added a comment - We agree with many of the suggestions included in this thread: Ability to resize column width within queues just like it can be done in filters Give users the option to define whether column values wrap lines Allow users to expand / collapse columns The biggest pain point right now is column width, so hopefully that would be given priority.

            +1

            Jake Zubov added a comment - +1

            Hi everyone,

             

            We noticed that this improvement wasn't delivered for a while. So while these features are not available natively in Jira, and if you're open to using a third-party app, I would like to present an alternative solution - Mindpro Lineup Cross Project Queues for JSM (https://mindpro.solutions/lineup-app)

             

            Mindpro Lineup is a cloud app for Jira and JSM that allows you to create, share and manage cross-project queues containing issues from multiple service desks. In a nutshell, with this app, you can:

             

            • Create cross-project queues from multiple portals
            • Import queues from Jira Service Management projects
            • Configure queues' visibility and access using group-based permissions
            • Prioritize issues and add queues in a Team Priority section
            • Customize specific columns for each queue view (size, type, etc..)
            • Search and filter issues inside the queue with dynamic filters
            • Save filters and add custom tabs views inside queues
            • Create a multi-level structure of groups (folders) to organize queues better
            • Hide unused queues for better clarity and team focus
            • Setup advanced permissions for specific groups to create, edit and manage queues
            • Learn more at: https://mindpro.solutions/lineup-app

             

            Ps: We understand that adding more plugins or paying more for certain features is not always feasible when they should be native. However, if you're open to using a third-party app, we can grant you up to 50% off your license for up to one year. To do so, use the following discount codes (according to your billing cycle): Monthly Billing code: MQSMLINEUPMONTHLY or Annual Billing code: MQSMLINEUPANNUAL

             

            Regards, 
            Eduardo from the Mindpro team

            Eduardo Oliveira - Mindpro Apps added a comment - Hi everyone,   We noticed that this improvement wasn't delivered for a while. So while these features are not available natively in Jira, and if you're open to using a third-party app, I would like to present an alternative solution - Mindpro Lineup Cross Project Queues for JSM ( https://mindpro.solutions/lineup-app )   Mindpro Lineup is a cloud app for Jira and JSM that allows you to create, share and manage cross-project queues containing issues from multiple service desks. In a nutshell, with this app, you can:   Create cross-project queues from multiple portals Import queues from Jira Service Management projects Configure queues' visibility and access using group-based permissions Prioritize issues and add queues in a Team Priority section Customize specific columns for each queue view (size, type, etc..) Search and filter issues inside the queue with dynamic filters Save filters and add custom tabs views inside queues Create a multi-level structure of groups (folders) to organize queues better Hide unused queues for better clarity and team focus Setup advanced permissions for specific groups to create, edit and manage queues Learn more at: https://mindpro.solutions/lineup-app   Ps: We understand that adding more plugins or paying more for certain features is not always feasible when they should be native. However, if you're open to using a third-party app, we can grant you up to 50% off your license for up to one year . To do so, use the following discount codes (according to your billing cycle): Monthly Billing code: MQSMLINEUPMONTHLY or Annual Billing code: MQSMLINEUPANNUAL   Regards,  Eduardo from the Mindpro team

            Yes, please.

            Elena Matei added a comment - Yes, please.

            Jake Urman added a comment -

            I would love to have this functionality added. 

            Another thing that could work would be to have an option to not allow multiple lines/word wrap for these entries. 

            Jake Urman added a comment - I would love to have this functionality added.  Another thing that could work would be to have an option to not allow multiple lines/word wrap for these entries. 

            Same here, resizing would be very nice - or to specify a maximum character/text length would be nice. Otherwiese we have to remove for example the Request type to have a clear view:

            Constantin Lotz added a comment - Same here, resizing would be very nice - or to specify a maximum character/text length would be nice. Otherwiese we have to remove for example the Request type to have a clear view:

            Yes

            Takia Gordon added a comment - Yes

            yes

            Avarice Guerrero added a comment - yes

            yes!

            Yes please!

            Spriggs, Dillon added a comment - Yes please!

            Emily Wood added a comment -

            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

            Emily Wood added a comment - 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

            Yes, much needed.

            ccastillo@netcoresolutions.com added a comment - Yes, much needed.

            yes please - devs get on the case and implement this.

            Robin Sutton added a comment - yes please - devs get on the case and implement this.

            Tay Jacobe added a comment -

            Completely agree that this would be a hugely helpful feature. Usability for queues (and filters, if the same feature was adopted) would be greatly improved if we could adjust column widths. 

            Tay Jacobe added a comment - Completely agree that this would be a hugely helpful feature. Usability for queues (and filters, if the same feature was adopted) would be greatly improved if we could adjust column widths. 

            Any news? That could be a quick win for everyone IMHO...

            Nicolas Esteves added a comment - Any news? That could be a quick win for everyone IMHO...

            this will be such a handy feature to have available.

            Robin Sutton added a comment - this will be such a handy feature to have available.

            Great feature what would help a lot! Thanks

            Thomas Drost added a comment - Great feature what would help a lot! Thanks

            Would be a great feature and would help a lot! Please add it to your to-do list.

            Thank you

            Tom Macpohl added a comment - Would be a great feature and would help a lot! Please add it to your to-do list. Thank you

            This would be highly useful. Please add this asap, thank you!

            Florian Gruppe added a comment - This would be highly useful. Please add this asap, thank you!

            Very interesting feature, please add it.

            Patrick Jarzabek added a comment - Very interesting feature, please add it.

            This is something that my team are keen to see happen asap

            Gavin Klose added a comment - This is something that my team are keen to see happen asap

            This is still pending ?

            Vijay Kumar Bhupananpati added a comment - This is still pending ?

            Please add this feature, it's so basic yet so critical

            Konrad McClure SW added a comment - Please add this feature, it's so basic yet so critical

            James Carn added a comment -

            Can we increase the priority of this issue - this is very basic functionality that every other app has.....

            James Carn added a comment - Can we increase the priority of this issue - this is very basic functionality that every other app has.....

            This is desperately needed!

            IT seems like something that would be included by default,
            not something that has to be requested and then waited upon for years...

            Small fields that would require 75px get assigned 300px or more, 
            shifting the entire focus of the board to the right, and pushing stuff like dates off the screen.

            Please consider changing this soon!

            Deleted Account (Inactive) added a comment - This is desperately needed! IT seems like something that would be included by default, not something that has to be requested and then waited upon for years ... Small fields that would require 75px get assigned 300px or more,  shifting the entire focus of the board to the right, and pushing stuff like dates off the screen. Please consider changing this soon!

            Yup this is not a good layout for us.

            The nature of our summary makes it usually around 150 characters... this has to word wrap to several lines... whereas I have another field that is usually only 5 or fewer characters... and it has a mass of empty space.

            Please add this functionality.

            Michael Stanmore added a comment - Yup this is not a good layout for us. The nature of our summary makes it usually around 150 characters... this has to word wrap to several lines... whereas I have another field that is usually only 5 or fewer characters... and it has a mass of empty space. Please add this functionality.

            Kim My added a comment -

            Agreed. We're only using the basic service desk queue headers: Key, Status, Assignee, Summary, Created, Reporter, and Labels. It used to be that with these headers we could see all issues single-spaced more compact view, but now everything is double-spaced unless we get rid of one of these headers. This could be fixed if we could either change the sizing of the field or decrease the size of the field (since there's a lot of blank space). It looks just fine on edit view, but wish it would reflect on the production end of it.

            Kim My added a comment - Agreed. We're only using the basic service desk queue headers: Key, Status, Assignee, Summary, Created, Reporter, and Labels. It used to be that with these headers we could see all issues single-spaced more compact view, but now everything is double-spaced unless we get rid of one of these headers. This could be fixed if we could either change the sizing of the field or decrease the size of the field (since there's a lot of blank space). It looks just fine on edit view, but wish it would reflect on the production end of it.

            Mike Loux added a comment -

            Yes, please.  The new, ahem, expanded Service Desk queue view was sprung on us all of the sudden, with the announcement that "spacing on the columns [is] an expected behavior on the new UI in order to enable new functionalities in the future".  Charming.  Is this a part of the new "simplified" issue view (which is anything but, since we have to go hunting for all the stuff that we used to have at a glance, thereby making us less efficient)?  So.  Much.  Winning.

            Mike Loux added a comment - Yes, please.  The new, ahem, expanded Service Desk queue view was sprung on us all of the sudden, with the announcement that " spacing on the columns [is]  an expected behavior on the new UI in order to enable new functionalities in the future ".  Charming.  Is this a part of the new "simplified" issue view (which is anything but, since we have to go hunting for all the stuff that we used to have at a glance, thereby making us less efficient)?  So.  Much.  Winning.

              Unassigned Unassigned
              tbehm@atlassian.com Thiago Behm.
              Votes:
              139 Vote for this issue
              Watchers:
              85 Start watching this issue

                Created:
                Updated: