Guide · Jira Cloud Standard
Promote workflows without Premium sandbox deploy
Atlassian’s sandbox configuration deploy is a Premium or Enterprise path. Most Cloud sites are on Standard or Free. Those admins still need to move company-managed workflows. Here is a workflow-only path that does not wait on that beta.
30-day trial · Free for teams ≤10 · then about USD 2/user/mo
Related: sandbox to production Related: vs Workflow Wizard Easy Workflows app page01 — The plan gap
What Standard does not include
Atlassian documents “deploy configuration changes from a sandbox” for Premium and Enterprise. On Standard you do not get that native promote. You also do not get Data Center XML export, and Cloud still has no built-in workflow file import between sites.
If you only need the workflow (not screens, fields, issues, or a full config manager), you can still move it: export JSON, validate on production, import when Ready, keep a snapshot.
02 — Safe sequence
Export, validate, then write
- Export the company-managed workflow or scheme as portable JSON from the source site.
- Scan for statuses, custom fields, and third-party rules that will not survive.
- Validate on the target in read-only mode. Stop on blocking errors.
- Import only when the verdict is Ready.
- Restore from a snapshot if the import is wrong.
03 — Honest limits
This is not a full config manager
This path is for company-managed Cloud workflows. It is not team-managed workflows, Data Center XML, or a copy of whole projects and issues. For screens, fields, and every scheme type, use a configuration manager or Atlassian’s Premium sandbox deploy.
04 — Tooling
Easy Workflows for Jira
Easy Workflows for Jira is a Forge app for that workflow-only path. Definitions, snapshots, and history stay in your site. Marketplace: Easy Workflows for Jira. Support: info@berkly.nl.