Validate before you import a Jira Cloud workflow

01 — Why validate first

Import without a verdict is how production breaks

Cross-site or restore-style imports fail when the target is missing statuses, custom fields, or third-party conditions/validators/post-functions that the source relied on. Writing first and debugging afterward means users already hit broken transitions. The safer habit: run a read-only validate on the target, read the verdict, fix blockers, then import only when Ready.

02 — Verdict first

Ready to import vs blocking errors

• Ready to import — no blocking errors. You still review the create/update/reuse plan (what will be created, updated, or reused on the target) before you confirm the write.
• Blocking errors — do not import. Typical blockers: statuses that do not exist on the target, required fields missing, or rules tied to apps that are not installed on the destination site.
• Warnings / re-add checklist — built-in rules often survive; third-party app rules usually need a re-add checklist after a successful import. Warnings are not a green light to skip the Ready check.

03 — What the plan shows

Create, update, and reuse — before anything writes

1. Scan the package for statuses, fields, and third-party rules that may not survive.
2. Validate on the target in read-only mode — nothing changes on the live site until you confirm.
3. Read the verdict first (Ready vs blocking), then the scannable summary, then the full create/update/reuse plan.
4. Fix blockers on the target (or adjust the package), re-validate, and only then import.
5. Keep a snapshot before the write so you can restore if something still goes wrong after Ready.

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

Validate vs export/import vs move vs rollback

• This guide — read the Ready / blocking verdict and the plan before any write.
• Export / import — portable JSON path, native Copy vs full CM vs workflow-only.
• Sandbox → prod move — promote a tuned company-managed workflow between sites.
• Rollback — restore a pre-change snapshot after a bad write, then re-validate.

06 — Tooling

Easy Workflows for Jira

Easy Workflows for Jira is a Forge app built for that validate-before-write path: export portable JSON, read-only preview 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