• 185
    • 11
    • 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.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      The driving use case for this request is essentially the same as JSD-285, but rather than grouping queues, it would be preferable to be able to show/hide Queues. Many of our groups never need to be able to see queues other than their own, and the grouping ability would not really reduce the density of the Queues page for them.

      Much like Jira Filters can be shared, it would be great if Service Desk allowed queues to made available to specific users/groups or everyone.

       
      Workaround 

      • We can implement access restrictions to queues by leveraging the Jira Issue Security Feature.

      https://confluence.atlassian.com/display/JIRAKB/How+to+Restrict+Access+to+Queues+in+Jira

          Form Name

            [JSDCLOUD-366] Ability to show/hide Queues with specific users/groups

            We need this. Would make a huge difference!

            Judy Forrister added a comment - We need this. Would make a huge difference!

            eb added a comment -

            needed here

            eb added a comment - needed here

            Rahil added a comment - - edited

            Is this pending since 2014? Whats the current status of this request?

            Rahil added a comment - - edited Is this pending since 2014? Whats the current status of this request?

            We just moved to Jira, disappointing our previous system that was very basic could do this, Yet Jira cant

            Michael Yenco added a comment - We just moved to Jira, disappointing our previous system that was very basic could do this, Yet Jira cant

            when will implement it?!!!! Other service desk platforms have this feature but no JSM! Very disappointed on this

            low jian liang added a comment - when will implement it?!!!! Other service desk platforms have this feature but no JSM! Very disappointed on this

            Aslam K M added a comment -

            Workaround 

            • We can implement access restrictions to queues by leveraging the Jira Issue Security Feature.

            https://confluence.atlassian.com/display/JIRAKB/How+to+Restrict+Access+to+Queues+in+Jira

            Aslam K M added a comment - Workaround   We can implement access restrictions to queues by leveraging the Jira Issue Security Feature. https://confluence.atlassian.com/display/JIRAKB/How+to+Restrict+Access+to+Queues+in+Jira

            Sushant Mulgaonkar added a comment - https://getsupport.atlassian.com/browse/JST-818008

            Was directed here after requesting the same thing through support and am dismayed to see it's been an outstanding request for so long. This is really a basic feature and is unfortunate it's not available. 

            Geoffrey Frock added a comment - Was directed here after requesting the same thing through support and am dismayed to see it's been an outstanding request for so long. This is really a basic feature and is unfortunate it's not available. 

            Nico added a comment -

            I am puzzled that this isn't already a feature. It seems like a feature that everyone would want. For example, I want to be able to see all my open requests, and the ones owned by some people on my team, in addition to unassigned ones with certain attributes. No other person would want the same view and I don't want to clog up the list of queues.

            Nico added a comment - I am puzzled that this isn't already a feature. It seems like a feature that everyone would want. For example, I want to be able to see all my open requests, and the ones owned by some people on my team, in addition to unassigned ones with certain attributes. No other person would want the same view and I don't want to clog up the list of queues.

            nshawcross added a comment -

            Agents have the ability to cherry pick issues at the moment and they are working issues that are not for their team. If this tool is a serious contender for a contact center system it needs to have this.

            nshawcross added a comment - Agents have the ability to cherry pick issues at the moment and they are working issues that are not for their team. If this tool is a serious contender for a contact center system it needs to have this.

            Milena, the Queues plugin does not work well. It doesn't work on mobile, and it's a completely separate interface you have to enter to use the queues. It's nowhere near as good as the native UI/interface - it's a workaround at best. Atlassian either needs to allow marketplace apps to have deeper integrations into Jira, or implement the feature themselves.

            David Washburn added a comment - Milena, the Queues plugin does not work well. It doesn't work on mobile, and it's a completely separate interface you have to enter to use the queues. It's nowhere near as good as the native UI/interface - it's a workaround at best. Atlassian either needs to allow marketplace apps to have deeper integrations into Jira, or implement the feature themselves.

            we neeeeeeeeeeeed this!!!!! now!!!

             

            the add on mentioned above doesn't achieve the desired results!!!

            Katlego Masanabo added a comment - we neeeeeeeeeeeed this!!!!! now!!!   the add on mentioned above doesn't achieve the desired results!!!

            need this

            Mark Anderson added a comment - need this

            There is an add-on that will solve your problem: https://marketplace.atlassian.com/plugins/com.intenso.jira.queues-extension/server/overview

            Regards, Milena

             

            Milena Lech added a comment - There is an add-on that will solve your problem:  https://marketplace.atlassian.com/plugins/com.intenso.jira.queues-extension/server/overview Regards, Milena  

            we need it tooo!!

            samira malekpour added a comment - we need it tooo!!

            We need it!!

            Elieser Guterres added a comment - We need it!!

            yes, we need this function as well. Managers need to approve requests assigned to them. Without this function it is hard for them to locate the tickets if full URL is not provided.

            Hailin Zhang added a comment - yes, we need this function as well. Managers need to approve requests assigned to them. Without this function it is hard for them to locate the tickets if full URL is not provided.

            CollinM added a comment -

            Our service team is also big and the volume of queues we need to make because of current functionality
            is a real pain. We have a central call center where all IT help desk calls are taken. They then triage the calls
            to the appropriate IT teams at the corporate office (Networking, Systems, Production, Dev, DBA, Web etc..)
            They can also triage the tickets to the local unit if we have IT staff there. We have over 150 locations with
            IT techs. So the current solution also makes us reference an external document to know which tech works where and
            run the risk of assigning a ticket to someone local who may be out of office and not able to see it.

            CollinM added a comment - Our service team is also big and the volume of queues we need to make because of current functionality is a real pain. We have a central call center where all IT help desk calls are taken. They then triage the calls to the appropriate IT teams at the corporate office (Networking, Systems, Production, Dev, DBA, Web etc..) They can also triage the tickets to the local unit if we have IT staff there. We have over 150 locations with IT techs. So the current solution also makes us reference an external document to know which tech works where and run the risk of assigning a ticket to someone local who may be out of office and not able to see it.

            FYI This would be SUPER useful for our organization. We would love to see this because our service team is big and we are dividing up their responsibilities significantly and cannot manage the volume of queues we have with them being accessible to everyone on the team. Thanks!

            Sara Wajnberg added a comment - FYI This would be SUPER useful for our organization. We would love to see this because our service team is big and we are dividing up their responsibilities significantly and cannot manage the volume of queues we have with them being accessible to everyone on the team. Thanks!

              mchaudhry Megha
              052065e2dd28 Erik Berg
              Votes:
              229 Vote for this issue
              Watchers:
              148 Start watching this issue

                Created:
                Updated: