This would be incredibly helpful.  If nothing else, export to a template and import into the other projects.

What about this year? Or the situation is still stable (not moved even a step)? 

We wanted to create a template in Service desk so that our customers could fill it in a way and then forward the issue to another project to QA/Development. How hard can it be, right? Well... Issue templates are not supported in Service desk, Forms - are, looks kinda good, but then there's this current issue created back in 2014  

We don't want to create a Description2 field with this template and then create automations to copy it's content+hide/show fields etc... especially when looks at the bills from Atlassian

I created a bunch of forms in a test project (on a production instance), and I was able to copy those forms to the main project. Nice! Then I thought, there shouldn't be any problem copying the underlying request type, right? No! Argh! Where's the "copy to project" function that the forms have?! Can't find it. Google, google, google. Nothing. I come across this feature request. Wtf!

Very useful.
+1

Our team needs this too. We've created several JSMs with similar purposes and want to merge them. Recreating each request type and associated form is unnecessary work.

Need this. 

+1

Any update on this please? This feature is required to resolve our use case. 

Any update on this?

Hi a9a24189d84c and 9ccb215f7b45,

I can confirm that this is work that is actively being prioritised but not currently being worked on as of now. We are aware that creating projects with shared configuration doesn't fully solve this problem. 

We are looking to do this in the coming months, however, but do not yet have a clear date. 

This work has been prioritised below the ability to change the issue type of a request type (we are releasing a new feature that will eventually allow you to change the workflow of a request type to any workflow on your instance) and the ability to access all fields from within the request type configuration page (without needing to modify screens). 

Once these pieces of work are complete, we hope to work on this feature. 

Best regards,

Jehan Gonsalkorale

Product Manager, Jira Service Management

Hi @jehan,

Using the shared config, request types gets copied over; but using Automation with POST API method doesn't copy over the request type.

@jehan Is the ability to copy request types across projects being worked under this ticket or is there another we need to be watching?

Hi all, quick update here. 

We have released the ability to duplicate request types within a project and are actively working on the ability to copy request types across projects but are unable to provide an ETA yet. 

Learn more about duplicating request types within a project here: https://community.atlassian.com/t5/Jira-Service-Management-articles/Duplicate-request-type-available-in-Jira-Service-Management/ba-p/2026362

Otherwise, when a project is created with shared configuration, the request types are copied, so this is a useful extension to that feature, should you wish to use a project as a template and modify copies of generic request types. 

I'd love to hear any feedback you have on this. 

Best regards,

Jehan Gonsalkorale

Product Manager, Jira Service Management

+1

+1

+1 yes please!  

Hi all, 

Thanks for your interest here. We are working on this right now and hope to have this out in the coming months. We will provide updates in the coming weeks. 

Best regards,

Jehan Gonsalkorale

Product Manager, Jira Service Management

It will surely save time when the similar request type is being asked to create in the Service Desk.

+1 

For those wanting a work around, I found one using the legacy automation as it still has the ability to set a request type. Please see steps below;

1. Create the clone in the new Jira Automation

When issue is created, clone to Y project
Then permanently deleted

2. Create a new custom field, I called it "Request type picker"

Using a single picker with multiple options, add all your request type names from your project the tickets will be deleted from

3. Go to the project the tickets are being created and deleted

Go to the settings, request types and add the customer field you just created, hide it so it automatically selects the option with the same name as the request type. So if the request type is called "IT Support" you would have the custom field "Request type picker" automatically set to "IT Support"

4. Go to the project the tickets are being cloned onto

You want to make sure all the request types you created on the other project are also mirrored on the main cloned to project

Using the legacy automation on the project (Not available for Jira instances created after 30th of Aug 2021 as Jira is discontinuing), create automations for each request type. It will look like this:

When this happens...
       Issue Created

If these match...
      Issue Matches:
"Request Type" is Empty AND "Request type picker" = "IT Support"

Then do this...
     Edit request type name to "IT Support"

 Its a big shame Jira are stopping legacy automation when Automation for Jira has so many glaring flaws like this one.

Hope this helps some of you

Chris

+1 hoping this is close to implement?

Is there still no work around for this? No way to export and then import again? What about via API?

I have multiple service desks that use the same request types and setting them up over and over again is frustrating. 

+1 

+1

Hi all,

We have re-opened this ticket as the new feature we released (that copied existing request types when you created a ticket with shared configuration) does not allow you to copy request types across two existing projects. This is something we are considering and will provide more updates on this in the coming months.

Kind regards,

Jehan

What about cloning a request type within an already existing project? 

When will this apply to next gen service desk as per original comments from Rachel? When did scope change to classic?

Hi everyone,

Thank you for your patience. I am excited to announce that, as of today, we have released a feature that would let you clone an existing classic JSD project. From now on, if you created a project using the 'Share settings with an existing project' option, you will get a near exact copy of the existing project, including all request types, queues, SLAs, reports etc.

Try it out and let us know your feedback. Note that this feature applies to classic service desk projects only.

Regards
Vidhu

Hi everyone, 

I'm re-posting this survey, so we get more insights around what you want from a Copy Project feature in JSD next-gen. If you feel strongly about this feature, please don't miss out on sharing your thoughts! 

https://forms.gle/gh1iBzoeBy2yckEF6

Additionally, if you want to have a chat, don't hesitate to email me via rlin2@atlassian.com .  

Thanks again!
Rach 

Hi Esther, 

We are currently looking at including this feature for next-gen projects specifically. Classic has shared schemes which allow you to centrally manage your request types, as well as the ability to share setting with an existing project when you create a Classic project. 

Thanks!

Rach 

Hi, Rachel - I'm glad this is being looked at, but, as I'm sure you're going to hear from many of us, will it also be available for classic SD projects? 

Hi everyone, 

My name is Rachel and I’m a Product Manager working on simplifying Jira Service Desk’s project configuration. I'm currently looking into a Copy Project feature in next-gen and would love to get your feedback in terms of what you expect from this capability. At a high level, this will enable the ability to copy/clone JSD project configuration from an existing project to allow faster setup and manage work at scale.

Please share your thoughts with us through this survey: https://forms.gle/hmmLuR954afg4UtD6 

This will be extremely valuable in shaping the product. If you're keen to chat more in-depth, please reach out to me via rlin2@atlassian.com and I'm happy to set up a call  

Really appreciate your feedback!

Rach 

This feature is crucial!

I just committed to Jira Service Desk, and I see now this is going to completely run me out of time with the amounts of projects I have to create.

After 4 years this funktionality still has been not implemented?  

Is there another way of doing this that I am missing?

I think I may be to first one to comment on this feature request in 2018. Is there any update on this? I noticed it is not assigned to an engineer, when can I expect an update?

This would save a lot of man hours, as the most time consuming part of on-boarding a customer is building their request types, by far. 

Any update on this issue? pretty straight forward 

Please we damn need it !

Come on Atlassian - this would be a great feature & plus point for everyone, particularly if the "Visible fields" are included in the clone or copy function!!!  

we need this feature

I agree this is an absolute must & it is getting to the point now where I may have to swap out to another product!!!!

Yes - I have multiple external customers that need to use the same request types. Being able to have a shared request type group that I can assign, or the ability to copy the group would be so productive!  Much better than creating them over and over again.  Please!

Does anyone know of a plugin or any obscure way of doing this? I built new service desk request forms in a dev environment but have no way to copy it to production.

Why is nobody of atlassian commenting on these topics? Copying templates, request types, etc. is one big topic for the service desk functionality. It's still focussed on internal help desks only. Which is a shame. Since you can use it as an external helpdesk for your customers just fine, but the lack of copying service desk request types or total projects is making it almost unusable for companies with many customers.

Not being able to copy request types is really time consuming. It would be so much easier to just copy one and then tweak it depending on what the differences are. Right now, I have to copy and paste all the field helps, descriptions etc. Some of them are 75% the same as all the others.

"request type schemes" or at least, a copy included with "create with shared configuration" would be a great time saver.

Something analogues to the Workflow / Screen / Issue Type schemes would be great.
Then you can even change the scheme and update the Request Type of all the Desks.

I understand that each desk should have isolated configs so that each desk admin can configure the desk the way they please.
Maybe an option to link to a scheme and if the desk admin changes the types they decouple from the scheme. (After a warning of course)

We are setting up a service desk for each of our external customers. Having a custom template for the Request Type or being able to copy an existing one that we can reuse multiple times would be HUGE time saver. The way it is now, I have to manually create this for each one because the standard ones that are added by default are not useful.