Home

Products

Configuration Manager for Jira (CMJ)

Configuration Manager for Jira (CMJ)

Manage Jira configurations 

with logo-configuration-manager-cmj-header-delete confidence

Manage Jira configurations 

with logo-configuration-manager-cmj-header-delete confidence

Preview and deploy updates, back up configurations, and standardize project setups across cloud sites. Maintain control over every change.

Preview and deploy updates, back up configurations, and standardize project setups across cloud sites. Maintain control over every change.

Try for free
Try for free
Book a demo
Book a demo

Production protection iconProduction protection

Snapshot compare iconSnapshot comparison

Controlled deployment iconControlled deployment

Configuration governance iconConfiguration governance

Key benefits 01

Production protection icon

Protect production changes

Review every Jira configuration change in a lower environment, then promote only the approved scope to production.

Move configurations icon

Stop rebuilding by hand

Move Jira configurations between environments using reusable configuration packages called snapshots, reducing repetitive manual setup.

Snapshot compare icon

See differences before release

Compare configuration changes with the target site, identify dependencies and warnings, and customize how changes are applied.

Consistent environment icons

Keep environments consistent

Schedule recurring snapshots as a Jira configuration backup, then compare versions to identify drift and support configuration governance.

Configuration icon

Preserve configuration evidence

Maintain point-in-time configuration records that support change reviews, audits, CMDB processes, and administrator handoffs.

Control restructure icon

Restructure with control

Consolidate, split, or scale project configurations across cloud sites with clear scope, dependencies, and customization options.

Teams who trust us

Key features 02

Bring enterprise-grade control to every configuration change

Deploy only the configurations you need

Select specific Jira project configurations and their required dependencies, to keep deployment focused on the changes your team needs.

Select specific Jira configurations and their required dependencies

Customize configuration mapping

Adapt supported configurations to the target site with custom mappings and transformations, resolving differences before deployment to reduce manual rework.

Map Jira configurations to the target environment before deployment

Schedule configuration backups

Automatically back up Jira configurations, compare versions to identify drift, and maintain clear evidence for configuration governance and audit reviews.

Schedule Jira configuration backups and retain snapshot versions

Analyze snapshots without deploying

Compare versions of the same snapshot scope to investigate drift, check configuration standards, and gather audit evidence without starting a deployment.

Compare versions of the same snapshot scope to investigate drift, check configuration standards, and gather audit evidence without starting a deployment.

How CMJ works 03

Configuration control

See what changes, control what moves, and keep every decision traceable.

Explore features

Create snapshots

Analyze impact

Resolve conflicts

Deploy approved scope

Compare versions

Schedule snapshots

Create a granular CMJ Cloud snapshot with required dependencies

Capture only the configuration you need

Select individual projects and configuration elements, or capture all supported configurations. CMJ Cloud automatically includes required dependencies. Create snapshots on demand or schedule recurring versions to keep a configuration record over time.

Review differences between CMJ snapshot versions

Know what will change before it moves

Run a pre-deployment analysis to identify additions, modifications, warnings, errors, and affected configuration before anything reaches the destination site.

Resolve Jira configuration conflicts before deployment

Resolve configuration conflicts before release

Use inline or bulk transformations and supported mappings to address errors and align source configuration with the destination. Rerun analysis to confirm the deployment is ready.

Deploy approved Jira configuration and review results

Promote approved changes to production

Deploy reviewed snapshots to the same or another Jira Cloud site. For large deployments, enable Slack notifications to stay informed of the outcome whole your team continues working.

image

Explain how configuration changed

Compare two versions of the same snapshot scope. Review objects that are unique, different, or identical to identify configuration drift or prepare for audits.

Schedule recurring CMJ configuration snapshots

Maintain a recurring configuration record

Schedule recurring snapshots of a defined configuration scope without recreating them manually. Compare versions to track changes over time and maintain a consistent record for governance and audits.

“Deployments used to be nerve-wracking, but with CMJ, I can preview and validate changes before applying them.

This not only saves time but also minimizes risk and ensures the team’s workflow remains uninterrupted.”

MD D.

“I really appreciate the seamless operation of CMJ.

Its efficiency has significantly reducced the time and effort we previously spent on monitoring and handling individual configurations steps.”

Samriddhi G.

“This tool is a lifesaver when you need to migrate changes from staging to production instances.

Its support is prompt and valid. It's a must-have.”

Stefano C.

Resources 05

Resources

FAQs 06

FAQ's

CMJ Cloud helps Jira administrators capture supported project configurations in snapshots, analyze changes against a destination site, and deploy the approved scope. Scheduled snapshots and version comparison also support ongoing configuration governance.

CMJ is designed for enterprise Jira administrators, Atlassian platform teams, change and release managers, governance stakeholders, and solution partners responsible for complex or business-critical Jira environments.

Yes. CMJ is a Jira deployment app for teams that need to analyze, validate, and move supported configuration between environments. It's a strong fit for complex Jira estates, frequent changes, multiple sites, and governed production releases.

CMJ packages supported configurations into snapshots, analyzes the changes against a destination site, identifies warnings and errors, and lets administrators resolve supported conflicts before deploying the approved scope to production.

A CMJ snapshot is a packaged state of supported Jira projects and configuration elements. You can deploy it to another site for sandbox-to-production promotion, retain it as a point-in-time reference, or selectively redeploy captured configurations to the same site. Redeployment does not automatically delete newer configurations.

With CMJ, you can migrate supported Jira configurations in four steps: capture the configurations in a snapshot, analyze changes against the destination, resolve supported conflicts and mappings, and deploy the approved changes.

A Jira configuration backup preserves supported workflows, fields, screens, schemes, and related settings in a CMJ snapshot. It does not include a complete backup of Jira work-item data, and selective redeployment is not a full point-in-time restore.

No. CMJ Cloud supports scheduled snapshots and version comparison, allowing administrators to review configurations drift periodically. It does not currently provide full proactive drift monitoring or configurable drift alerts.

CMJ Cloud requires supported Jira Cloud plans on the source and destination sites, CMJ licenses for both sites, Site admin or Organization admin permissions, and an Atlassian API token for authorization.