Compare two Jira Cloud workflows before you promote

01 — Why compare first

Promoting blind is how production surprises land

Sandbox and production rarely stay identical. Someone adds a status on staging, renames a transition on prod, or re-adds a third-party validator on only one site. Exporting and importing without a side-by-side read means you discover the delta after users hit broken transitions. The safer habit: compare staging vs production (or package vs live), then validate, then write.

02 — What to put side by side

Statuses, transitions, and rules

• Statuses — names and IDs that exist on both sites; missing statuses block a clean import.
• Transitions — from/to pairs, screens, and properties that differ between staging and production.
• Conditions / validators / post-functions — built-ins often survive; third-party app rules usually need a re-add checklist after promote.
• Create / update / reuse plan — after compare, a read-only validate should still lead with Ready vs blocking before any write.

03 — A promote loop that stays honest

Compare → validate → snapshot → import

1. Export the tuned company-managed workflow (or scheme) from staging as portable JSON.
2. Compare that package to the live production definition — side by side, not by memory.
3. Validate on production in read-only mode; fix blockers (statuses, fields, missing apps).
4. Snapshot production before the write so a bad promote is a one-click restore.
5. Import only when Ready, then re-check the same side-by-side view.

04 — Scope (honesty)

Company-managed only · Forge · not a full CM suite

This path is for company-managed Jira Cloud workflows. It is not a team-managed workflow tool, and it is not a full Configuration Manager for screens, fields, and every scheme type. Easy Workflows runs on Atlassian Forge (no egress by design): definitions, snapshots, and history stay in your site. Free for teams ≤10; 30-day trial; then about USD 2/user/mo via Atlassian. We do not claim to undercut Workflow Wizard at larger seat counts — pick the tool that matches the job.

05 — Which guide to open next

Compare vs validate vs move vs backup

• This guide — side-by-side staging vs production before you promote.
• Validate — Ready / blocking verdict and create/update/reuse plan before any write.
• Sandbox → prod move — promote a tuned company-managed workflow between sites.
• Backup — in-site snapshots and one-click restore.
• Copy between sites — workflow-only clone site-to-site.
• Standard plan — promote without Premium sandbox deploy.

06 — Tooling

Easy Workflows for Jira

Easy Workflows for Jira is a Forge app built for that compare-then-promote path: export portable JSON, side-by-side review, read-only validate with Ready / blocking verdict, import when you confirm, plus in-site snapshots and one-click restore.

Marketplace: Easy Workflows for Jira. Support: info@berkly.nl.

Try free on Marketplace