Testing new configuration to be released in Jira

[Mayur Gaikwad/Tech PMO]

Hi,

is there a best way with which i can check what all new feature or configuration when released for everyone to use can break or impact flow

for e.g a condition added at some step in workflow, how to check as how it may impact all other entities in a workflow. 

currently, i get huge requests at organisation level from different departments to make many customised changes and without testing i always have challenge that some things might break. Looking forward for some best practice that can be followed or with use of some plugins can this impact be identified? 

[Lior Neudorfer]

Hey @Mayur Gaikwad/Tech PMO ,

As other people suggested here, the best way to test changes like that would be on another Jira instance.

You can do that with the official Atlassian Sandbox (Premium only), but also with any other Jira instance (even a free one!), using the Salto app.

Using Salto, you can copy changes from your production Jira to any other site, make your changes there, test them, then automatically deploy them back to your production Jira.

Check it out here: https://marketplace.atlassian.com/apps/1225356/salto-configuration-manager-for-jira?tab=overview&hosting=cloud

Lior from Salto

[Dan Breyen]

Hi Mayur.  As I understand it, with the Premium or Enterprise Plans you get a sandbox that you can test stuff in.

I found this article w/ more information on them: sandboxes 

If anyone else knows more, I'm sure they will chime in. 

Hope that helps.

[Mayur Gaikwad/Tech PMO]

@Dan Breyen Anything for standard subscription?

[Dan Breyen]

There may be some third party thing, but nothing in the base application that I'm aware of.  Sandboxes only come with Premium and Enterprise.