Change management for Jira Service Management Standard Plan

[Susan Waldrip]

Hi,

I need to set up a Dev-UAT-Prod environment for Jira Service Management in the Cloud (UAT = User Acceptance Testing). Our org has the Standard Plan so we don't have a true Sandbox capability (comes with Premium and Enterprise) and Atlassian currently doesn't offer purchase of a separate Cloud Sandbox. I've looked at purchasing a separate Premium instance with a couple of licenses for Admins only and migrating tested changes on the Premium instance to the Production Standard instance but apparently that isn't available, either (please tell me if I'm wrong!). 

If you've successfully set up a change/release management environment for a Standard instance, I'd really appreciate any info and suggestions you have for using JSM, additional apps, and/or the processes you use to track and deploy JSM changes.

Thanks much!

[Matt Smith · Accepted solution]

For the Standard Plan to say it offers Service Management then there should be the capability of at least 1 sandbox for a chargeable instance.

I would ask that Atlassian review their policy on this urgently.

Free - No Sandbox

Standard - 1 sandbox per instance
Option for additional sandboxes at a price (month at a time).

Premium - Unlimited sandboxes.

How on earth can you safely develop and test new features properly without this.

Matt

[Susan Waldrip]

That's the Standard Plan users' conundrum, Matt -- and I like your plan, maybe Atlassian would consider it! If you enter a ticket for this, please let us know the number so we can  vote! 

But we can't be the only funds-strapped orgs out there who use Standard and need a safe process and environment for change and release management -- has anyone developed a solution for this?

[Matt Smith]

https://jira.atlassian.com/browse/ECO-166

I have raised the suggestion - Get voting Peeps !!

KR,

Matt

[Sean Riddle]

Salto works with all versions of JSM, Standard, Premium, or Enterprise

[Susan Waldrip]

Hi Sean, thanks for the info on Salto! Also, per your previous post, do you know if the multiple-sandbox release will include a Sandbox for the standard plan? I haven't seen anything in the community or on Atlassian's site that would indicate so but I could've missed it.

[Sean Riddle]

I'm not sure, my guess would be no because of the current sandbox limitations of Standard but I would definitely reach out to Atlassian to be sure.

[Alex Akilov]

If you have Premium, you get a sandbox (one for now, I've heard that multiple sandbox support is supposed to be released some time this year).  Unfortunately, I don't know if there is a way to migrate data easily from your existing standard instance to another instance.  May want to look at the Marketplace for solutions that provide backup or at least configuration management solutions so that you can at least replicate your configuration

[Susan Waldrip]

Thanks Alex, I've looked at Salto for Cloud (Salto.io) and CMJ (Appfire) but I believe they're targeted at JSM Premium with migrating JSM changes from Sandbox to Prod (Appfire did say they thought their product would work w/ Standard but to contact Atlassian, which I will do if the community responses aren't workable for us). I'm open to looking at other apps if you/others have suggestions!

[Alex Akilov]

Atlassian has a cloud to cloud migration tool that I was told will move data (including JSM) from one site to another.  Besides, Salto and CMJ, I've also seen a demo of Revyz which offers both config mgmt and data backup addons.

[Susan Waldrip]

Great suggestion re: Revyz, the product looks amazing and exactly the kind of thing I'm looking for. The backup/restore capability seems easy to use and almost every JSM element gets backed up. Unfortunately, this app also migrates changes site-to-site (like Salto and CMJ), and w/ the Standard plan we only have one site. But I will contact the Revyz team to see if they have suggestions for using their app in our situation, and I appreciate your help!

[Krista Stellar]

The cloud to cloud (recently changed to move product data) doesn’t do a full copy of the site data. In particular app data is not included (and custom fields added by apps won’t move). Plus product configurations (eg global permissions) are excluded. For your requirements the function offered by Atlassian will not work to simulate dev/uat/prod. I would consider the third party config management tools as the best approach. 

[Susan Waldrip]

That's good to know, Krista, thank you.

[Francis Mwebaza]

Hi, you can vist the support platform at support.atlassian.com

Hope you will get what you are looking for.

[Susan Waldrip]

Thanks Francis, if/when I do I'll follow up and post info.

[Sakhawat Hussain]

thanks for the info on Salto! Also, per your previous post, do you know if the multiple-sandbox release will include a Sandbox for the standard plan? I haven't seen anything in the community or on Atlassian's site that would indicate so but I could've missed it.

Regarding

Sakhawat Hussain

[Sean Riddle]

I honestly don't know at this point, my guess would be that Standard won't include access to sandboxes but I love Matt's suggestion above.

[Sean Riddle]

Salto is a good choice for configuration management and standardizing your release process. I believe Atlassian will be opening the beta for multiple sandboxes in mid-March