Transfer changes from Stage to Prod environment in Service Desk Cloud

Conny Lindberg

We are running JIRA Service Desk Cloud and have defined one project as Stage and another project as Production, both available on the same Atlassian domain URL. We separate the access by having different users configured for these two projects, employees to test and verify in Stage, and our customers defined in their respective organisation in the Prod project.

After verification of all new project settings (flows, fields, screens, email notification settings and text etc.) we want to push these to the Prod project. Of course this shall not impact any existing customer data (reported issues, organisations, registered emails etc.) in the Prod project.

What is the easiest way to achieve this? Sure we can try to keep an as detailed as possible changelog of all modifications done in the Stage project and then manually update the Prod project when time comes. This will however, at some point, result in a faulty Prod configuration due to human mistakes.

Can you share some best practises how you do this, as I assume many of you will need a similar setup.

Thanks!

Yevhen Rohovets

Hi, wow, it is interesting)

In the cloud version of Atlassian, there is no way to merge projects, schemes, and settings.

So, if your test project should become a production, then probably the easiest way is to follow these steps:
1) Create a new project, during creation, specify the creation of the shared configuration. This will be a new production.
2) Using a bulk change, transfer tasks from the current production to a new one (or clone them, it’s more correct)
3) Check what issues are moved to the current production
4) Configure access for customers for the new project
5) Accept changes at the organizational level, send out instructions for working with a new project

The disadvantages of such a project: you will lose the history of tasks (if you clone) and you will need to reconfigure some of the things. But as for me, this is the fastest option.