Guide · Jira Cloud
Back up Jira Cloud workflows in the site
Cloud does not give you a native workflow backup. A JSON file on a laptop is not a restore plan. Keep snapshots in Jira and roll back in one click. Free for teams ≤10.
Free for teams ≤10 · 30-day trial · then about USD 2/user/mo
Related: restore from snapshot Related: rollback after a bad import Related: compare before promote Related: vs Workflow Wizard Easy Workflows app page01 — The gap
XML export is gone
The old Cloud workflow editor could dump XML. That editor is gone. Native Cloud still has no “download this workflow and restore it later” path. If someone edits a production workflow and it breaks, you rebuild by hand or re-import a file someone saved on a laptop.
02 — A better backup
Snapshot in Jira, restore in one click
- Snapshot the company-managed workflow (or scheme) into the site before you import or edit.
- Validate a new import in read-only mode. Stop on missing statuses or third-party rules.
- Import only when Ready.
- Restore the snapshot if production is wrong. No hunting for last week’s JSON download.
03 — Restore when you need it
Keeping snapshots ≠ the restore job
This guide is how to keep daily and manual snapshots in the site. When production is wrong and you need to put a known-good definition back, open the restore from snapshot guide (pick snapshot → one-click restore → verify). After a bad import specifically, see rollback.
04 — Honest no
This is not issue backup
This is company-managed Cloud workflows only. It does not back up issues, team-managed workflows, or Data Center XML. For whole-project copy, use Atlassian Copy product data.
Easy Workflows for Jira keeps snapshots in the site (Forge). Try free: Easy Workflows for Jira. Support: info@berkly.nl.