Moving configuration changes between sandbox and production in Jira cloud

Configuration Manager for Jira (CMJ) by Appfire is designed to solve a wealth of challenges Jira administrators face. One of the most common uses of the app is for performing Configuration Change Management tasks within Jira, such as safely updating workflows, screens, and other project settings.

In the above video, you’ll learn how to use Configuration Manager for Jira to move changes from sandbox to production in Jira Cloud.

For more detail, visit our documentation page.

Looking for Data Center?

For step-by-step instructions on performing configuration change management in Jira Data Center using CMJ, visit this documentation page.

For your convenience, below is the transcript of the above video.

This is Kelsey from Appfire, and I am here to introduce you to Configuration Change management with CMJ Cloud.

If you manage Jira configurations, you know that change is constant. Workflows, permissions, and issue types need periodic updates to stay relevant with business needs. But making these changes safely, without breaking dependencies, can be tricky.

That’s why following a configuration change management process is essential. Every update needs to be tracked, reviewed and applied carefully to avoid errors, and that’s exactly what CMJ Cloud is built for.

It helps Jira admins manage large-scale configuration changes easily, without manual work or risky deployments.

Let’s dive into the app and how it can help you.

Step-by-Step walkthrough

Step 1: The change analysis screen – Instantly see what’s changing

One of the hardest parts of managing Jira changes is understanding the impact of making a single change. You might be updating workflows, modifying permissions, or rolling out new custom fields, but how do you know exactly what impact it will have across the application?

That’s where CMJ’s detailed change analysis screen comes in.

Instead of blindly pushing a change in production, CMJ’s detailed analysis gives you a clear breakdown of every change, with quick filters to jump straight to additions or modifications to your target system. This enables admins to thoroughly understand changes in sandbox environments and keep surprises in the production instance to a minimum.

You can instantly see what’s changing across your Jira instance, so you can make better decisions before applying anything.

Step 2: The detailed view – Less guesswork, more clarity

Even when you know what’s changing, it’s not always clear why it’s changing or what exactly is affected.

With CMJ’s Detailed View, you get a complete breakdown of every configuration related to a change.

Click on a workflow, a permission scheme, or a custom field, and you’ll see exactly what’s being added, modified, or removed.

Instead of guessing what’s happening behind the scenes, you can see every single change in one place before you apply anything.

Step 3: Mapping similar elements – Prevent duplicates & keep Jira clean

One of the biggest headaches in Jira administration is accidentally creating duplicate configurations when making updates. Over time, this leads to cluttered applications and unnecessary complexity.

With customizable configuration mapping, you can change how a source element is mapped to the target. For example, if you’re deploying a configuration to the target system that is similar in function to one that already exists, but their names don’t match, you can change the mapping so these become the same configuration after deployment.

This keeps your Jira setup organized, consistent, and clutter-free without manually comparing every setting.

Step 4: Draft mode & applying changes – No more surprises

Applying changes in Jira without CMJ can feel scary. Once you hit ‘save,' you have to hope everything works as expected. If something goes wrong, rolling back that change isn’t easy.

CMJ’s Draft Mode allows you to review and tweak changes before finalizing them. Plus, the info button gives you a quick breakdown of what each change will do before you apply it.

Instead of hoping for the best, you can see exactly what’s happening before anything goes live, reducing errors and last-minute fixes.

Step 5: JSON support for advanced users – Flexibility for every admin

Some Jira admins prefer using a scripts or a change file to apply bulk changes. CMJ also offers a JSON-based bulk transformations feature.

Admins who prefer a visual approach can use the UI to apply changes more easily.

Whether you love coding changes or prefer a point-and-click approach, you now have more flexibility to manage changes the way that works best for you.

CMJ Cloud makes configuration change management in Jira faster, safer, and more efficient.

Whether you’re managing a handful of projects or an entire organization, CMJ saves time and helps you avoid costly mistakes.

If you haven’t tried CMJ yet, click the link in the description to get a free trial!

Try Configuration Manage for Jira for free

How to perform change management tasks in Jira using CMJ

Subscribe for updates