Guide · Jira Cloud
Rollback a bad Jira Cloud workflow import
A bad import can leave missing statuses, broken transitions, or the wrong scheme on production. The safe path is snapshot before you change anything, restore in one click, then re-validate before you try again.
30-day trial · Free for teams ≤10 · then about USD 2/user/mo
Related: export / import guide Related: sandbox → prod move Related: Standard plan (no Premium deploy) Related: vs Workflow Wizard Easy Workflows app page01 — What “bad import” looks like
Statuses missing, transitions broken, wrong scheme
Typical failure modes after a workflow import: statuses that existed on the source are missing on the target, transitions point at the wrong statuses, validators/conditions/post-functions from third-party apps did not survive, or the wrong workflow scheme is now associated with the project. Users report they cannot transition issues, or boards show unexpected columns.
02 — Native options vs a pre-change snapshot
Why restore beats hand-editing production
On the same Cloud site, Admin → Issues → Workflows → Copy can help you branch a definition — but after a cross-site import already wrote changes, hand-editing the live workflow is slow and error-prone. A snapshot taken before import lets you put the known-good definition back in one step, then diagnose offline.
- No snapshot — reconstruct from memory, another site, or audit history. High risk on production.
- Pre-change snapshot — restore the previous definition, keep users unblocked, then fix the import package and re-validate.
03 — Rollback checklist (Easy Workflows)
Snapshot → restore → re-validate
- Before any import — take a manual snapshot of the target workflow (and keep daily backups on).
- If the import goes wrong — restore that snapshot in one click. Easy Workflows snapshots the previous definition before every update/restore, so you keep a trail.
- Re-validate — run validate-before-import on the package again (read-only). Fix blocking errors: missing statuses, fields, or third-party rules on the re-add checklist.
- Import only when Ready — then spot-check a test issue through the critical transitions before you call it done.
04 — Which guide to open
Export/import vs move vs this rollback guide
- Export / import — portable JSON path, native Copy vs full CM vs workflow-only.
- Sandbox → prod move — promote a tuned company-managed workflow between sites.
- This guide — undo after a bad write: restore snapshot, then re-validate.
05 — Tooling
Easy Workflows for Jira
Easy Workflows for Jira is a Forge app for workflow-only export/import with validate-before-write, daily and manual snapshots, and one-click restore. Definitions stay on Atlassian infrastructure. It is not a full Configuration Manager for screens and fields.
Marketplace: Easy Workflows for Jira. Support: info@berkly.nl.