If you leave this standard queues in your projects, they are still accessible for users. When you import queues to our app I recommend to remove old queues because they are not needed any more. 

Hi,

we built an internal addon, which allows the indiviual user to hide Queues for himself. Unfortunately, I am not sure, if I can publish it quite fast, as it has also other functionality baked in (which depends on JEMH), but if enough interest is here, I will give it a try. It looks like this (hope this works, alternatively: https://imgur.com/a/MRWce6R ):

Update:

Embedding didn't work, it is also server only at the moment

and what about original queues which are still accessible by users?

Hi Rohit,

Yes, this feature is available thanks to our app. You can import default queues created in Jira to our queues page (which is in global context) and you can use all options which are provided by our app.

Kate

Pawlak,

You are correct but its only for the queues which are available from the plugin but what about default queues created on Jira software itself.

How can we hide them from the users.??

Rohit

Hi,

In queue settings you should add groups in the field "Visible to groups". Users, who aren't in these groups, won't be able to see this queue.

"Hide"option is dedicated per user and allows to hide queue from general section. Thanks to it, this queue is not visible in the main section and is not loaded every time when you refresh the site.

Yes, you can manage only queues which are created in our app. But you can import default Jira queues in the easy way! Only click Import queues and select which you need.

If you still need a problem with configuration, please create a ticket on our[ Customer Portal|https://intenso.atlassian.net/servicedesk/customer/portal/1]. Our support will be happy to help you! They can also make a demo for you and tell you how to configure this app.

Cheers,

Kate 

It will be very useful to have ability to manage visibility of queues for specific users/groups.

The Intenso plugin can manage visibility but only for queues created with it. The default Jira queues remain unman-aged, unless you delete them.

i have downloaded the add on and it's a pain. not as simple as they make it out to be and doesn't achieve the results we want - which is hiding unnecessary queues for specific people.

Hi,

I don't really think that this add-on solves this issue, as it introduces another tab in the Navigation, instead of changing the queues in the main view. I still would like to see this feature.

Regards, Alex

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!!

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.

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!