You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?
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.
YAY! So creating a service desk with a shared configuration copies the portal? Fantastic, that's 99% of the effort in this case, thanks!
Yes I had a project where I needed to create 13 similar JSM projects. It was definitely a lifesaver.
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)