Please add this feature. I am surprised it is not there.  Setting up similar queues manually is cumbersome.

Please add this feature.

I have to setup multiple Jira SM Projects and this is really a pain to set all column manually.

We need it. In Jira Server you can do it, I don't understand why you delete this option in cloud.

Waiting too for this essential feature 

I second this. We have a ton of projects with multiple queues. Please Atlassian add this!

Definitely needed - this would save so much energy and time, especially on JSDs with lots of queues where using Jira Boards is not an option.

Very basic feature and will be very helpful. Very tedious to have to recreate queues that are simular.

Will be a quick win.

Hi, 

As apparently many users here, I have several Service Desk instances (1 per client, and it's mandatory for our purpose), but I do want to duplicate configured queues from 1 Service Desk (the basic one that we copy for all new child instances for project configuration) to all the others.

Today I've 12 JSD and when I want to modify 1 queue, I need to do it 12 times. Luckily, I "only" have 7 queues to manage for the moment..

Please consider adding the queue copy from one project to another and the availability to create the same queue for each project in once ! 

Best regards 

The queues setup is so bad, it is such a repetitive work to do that, why can't we have an option to define something for a start so we don't need to create every time the same columns or to copy a queue and than make changes so at least some of the setup is there.

@viktor There are plugins to do this. Atlassian would prefer you buy a plugin to do that. Why?

They didn't develop the plugin but they sure do skim off the top if you buy it via the Atlassian store. Why include basic features for base price when they can upsell?

EA microtransactions have nothing on the Atlassian Cartel.

Creating new projects with shared configuration is super tedious, since they dont have any queues.

When I think that I need 5-10 hours to maintain a service desk of 20 in total since:

1) Default columns just are not enough
2) Default filter is insufficient
3) copying after setting up 1) and 2) is not possible and we have to repeat this completely manually up to 20 times (since you have to adjust each created queue individually)

then I ask myself the price for service desk and imagine the vs. the administrative "user friendliness" of other systems.

What is needed umbedingt

• Copy and clone queues

• the possibility to create queues with the same name several times in order to use multiple queues per status eg topics / user-related

• Unify the columns on all queues or selected queues so that you do not have to repeat this "manually" "x times".

• The "new updates / comments" the ticket in the queue may be highlighted or the text is bold and in the eye. or an "ATTENTION" symbol is displayed

This is really need by the admin. I've set up so far 5 instances of Service Desk, and had to manually create upwards of 100 queues, tediously, manually.  Please get this on a roadmap.

The operation is unfortunately not really good, if you compare other ticket systems, such basic functions are standard. There are still "queues for jira" but this plugin makes no sense that you need a plugin for a basic function such as copying and cloning, but which still overrides the service desk in the sense "into a new dialog".

Implementing Jira is just like flying Spirit. Would you like some basics like water? I hope you brought your credit card.

Lure us in with a low price and then once we are stuck give us the shaft.

You know, I have to say it's pretty smart (like a fox!) of Atlassian to sell a product with a basic functionality and a well documented API, and let their skilled users do all of the hard work of creating and adding the features and functions that make the product stand out ahead of their competitors. It allows Atlassian to focus on new ways to make money rather than adding requested features to their existing products. Very clever!

Does the fact there there is an add-on mean that this feature won't be added to the core product?

@ dora.wang, @ Peter Hyde-Smith, @ Ferhat OZDAG, and all. I want to proudly announce that our Queues for Jira Service Desk app solves this problem - it includes a feature Copy queues. It is available for both Jira Server and Jira Cloud. Please check it on the Marketplace.

If you have any question, don’t hesitate to e-mail us at contact@intenso.support

https://marketplace.atlassian.com/plugins/com.intenso.jira.queues-extension/server/overview

Best regards,

Katarzyna

I have A project which have set up the queue with filter.
How can I export these queue to B project or C porject, so I won't need to copy & paste the same rules manually.

When will this feature will be add???

I am using JIRA for asset management. I would like to be able to use queues to filter my assets by different types & statuses, without having to hand jam all the fields I want displayed on each queue's layout.

Implementing Sub-queues or Nested queues would be awesome for organizing this as well. In fact, nested queues could maybe inherit the layout from their parent queues!

is there any update?

case is still unassigned.

who will handle this issue?

+10

there should be a way to setup which columns should be shown, save it as a view configuration, and then in each queue you make, be able to switch views at will

Surprised this isnt implemented - one of those expected features to keep queues layout the same and only change query criteria. Would be a big help.

+1

The ability to create a new queue by copying an existing one and making a few adjustments would be very helpful.

+1

@Luca Sokoll Service Desk Cloud - No Scriptrunner sigh...

@Adam Morrison can't you automate that with scriptrunner or something? That sounds mind bendingly horrible.

+1 I have to make 5 custom queues for 57 projects. Huge task.

+1

Is there any final date when we can expect this issue to be solved?

I agree - i really wondered that this is still not possible!

Tru dat! I agree. It's very monotonous to create several similar queues and it doesn't need to be.

Very usefull feature. When can we expect this?

Re-creating queues with very similar columns is very time consuming. This feature would definitely be useful!

Any movement on this? I can't see this being particularly difficult to implement and is a key feature in most other support desk clients...

Seriously! this would be extremely useful!

I second this. It may seem somewhat minor, but if you've got a lot of service desks and a dozen different queues and you want them to all be the same, thats a lot of work...