Hi All,

Per JSD 3.8 release notes:

Importing SLAs

Sometimes you need to create a new project, and you want to base it on an existing project. You can use an existing configuration when you create the project, but you can't use existing SLAs. Now you can import those existing SLAs, directly to your new project!

Simply go to your new project, access the project settings, followed by the SLA menu, and select Import SLA configuration.

Hope this helps a bit. If you have questions please refer to documentation or contact support.

Cheers!
Tim | Atlassian

Need this...

can you please provide the steps to clone or copy of  jira service desk instances?

Closing this one as a duplicate of the more voted JSD-191 so that we can have a clearer view on customers' needs and interests.

Cheers,
Lingbo

Hi, is there an update on this? I created a service desk project and would like to copy the configuration/settings/request types, etc to another project. Is an automated process for this available?

Thank you!

Why can't JSD use a same schema-based approach like Jira core?
Configuring service desks using shareable Request Type Schemas, Request Security Schemas, etc. would make this a non-issue, at least for us.

As a Business, there's nothing more useful than setting up a Service Desk template and be able to clone it as many times as needed to provide the same experience across a multitude of customers. Please implement this functionality, it will save hours, if not days, of admin time.

This has greater implications. When companies have a need for more than 1+ service desk, a copy feature is not only business critical, but usage of the product cannot be recommended in this scenario.

This would be very helpful.

This could be very useful in a scenario where you have a Service Desk project set up as a 'Proof of Concept' and would like to make a clone of it for production.

Please consider adding it!