Is it possible to create a clone of a JSM project including the portal and automation?

[Rob Horan]

I want to create a complex JSM project and it will essentially serve as a template for multiple JSM projects.

Is it possible to clone it, including portal and automation?

[Mark Segall]

Hi @Rob Horan - Yes and No.  When you create a project and copy the configuration of another project, it will maintain the portal settings and request types, but automation would need to be copied over.  Although it's an extra step, that's pretty straightforward with Jira Admin rights.  You can go to System >> Global Automation >> All Rules, find the relevant rules and copy them then change the project scope to the new project.

[Rob Horan]

YAY!  So creating a service desk with a shared configuration copies the portal?  Fantastic, that's 99% of the effort in this case, thanks!

[Mark Segall]

Yes I had a project where I needed to create 13 similar JSM projects.  It was definitely a lifesaver.

[Kelly Phillips]

Hi @Mark Segall 
How can we clone a JSM Project?

I have 2 environments, a dev and production (2 different urls).  I'd like to clone our production JSM project into our Dev environment.

Besides doing it manually, is there a more efficient way to do it?

[Stefan Froehlich]

Hi Rob,

I had a similar question but I am also wondering if the new projects keeps changes done to the original project in sync with the new project or if it only servers as a sort of Template?

Our plan is to create a UAT service desk for testing workflows and training, then once everything is confirmed and approved we create the production service desk but keep the UAT service desk for any future changes to be implemented and tested there first.

The Atlassian documentation isn't very clear about what is being cloned and what not and how those projects are then kept synchronized (if even)