Missing transition properties after Jira Cloud-to-Cloud copy

01 — What dropped

Statuses match; transition properties do not

Transition properties are the key/value pairs on a transition — things like opsbar-sequence, jira.permission.*, jira.i18n.title, and custom keys teams rely on for buttons, permissions, or integrations. After a site or project product copy, admins often see: transitions still fire, but the property map is empty, reordered, or missing keys the source had. That is a different failure mode from “import blocked on missing status” or “scheme still points at the old workflow.”

02 — Not the same as these guides

C2C property drop vs move / export / restore / scheme

• Copy between sites — intentional workflow-only clone with EW (export JSON → validate → import). Use that when you never wanted product copy.
• Sandbox → prod move — promote one tuned definition; not “fix properties after Atlassian C2C.”
• Export / import — portable JSON overview (native Copy vs CM vs workflow-only).
• Scheme promote — issue-type → workflow map is wrong; open that when associations drifted, not only properties.
• Backup / restore / rollback — snapshot safety net after you re-import; not the diagnosis of a C2C property gap.
• Standard plan / vs Wizard — plan and tooling choice; not this symptom.

This page assumes product copy already ran and transition properties on the destination are the gap.

03 — Recovery sequence

Compare → validate → snapshot → re-import (or scheme promote)

1. Compare source (or a known-good sandbox) vs destination side by side — look for property diffs on the same transition names, not only status graphs (compare guide).
2. Export the good company-managed workflow (or scheme) as portable JSON from the source with Easy Workflows — do not re-run product copy hoping properties reappear.
3. Validate on the destination in read-only mode — Ready vs blocking (statuses, fields, third-party rules) before any write (validate guide).
4. Snapshot the destination first so a bad re-import is a one-click restore (backup / restore).
5. Import when Ready — overwrite or update the thin post-C2C definition so transition properties come back with the JSON package.
6. Scheme check — if issue types still hit the wrong workflow after the definition is fixed, promote the scheme map next (scheme promote).
7. Verify — open critical transitions; confirm opsbar order / permission properties / custom keys; keep screens, fields, and automation on a separate checklist.

04 — Scope (honesty)

Company-managed · Forge · not a second product copy

This path is for company-managed Jira Cloud workflows (and schemes when the map also drifted). It is not team-managed, not Data Center XML, not issue/project copy, and not a promise that Atlassian Copy product data will preserve every transition property. Easy Workflows runs on Atlassian Forge: definitions, snapshots, and history stay in your site. Free for teams ≤10; 30-day trial; then about USD 2/user/mo via Atlassian. For full-site CM or Premium sandbox deploy, use Atlassian / CMJ / Revyz when that is the real need — EW is the workflow-only recovery slice after C2C drops properties.

05 — Which guide to open next

Property recovery vs C2C vs validate vs scheme

• This guide — transition properties missing after Cloud-to-Cloud / product copy; EW compare → validate → re-import.
• Copy between sites — workflow-only clone when you skip product copy.
• Compare — side-by-side before you overwrite the thin definition.
• Validate — Ready / blocking before any write.
• Scheme promote — fix issue-type → workflow wiring after the definition is sound.
• Restore — pick snapshot → one-click restore → verify.

06 — Tooling

Easy Workflows for Jira

Easy Workflows for Jira is a Forge app for that compare → validate → import path after product copy thins transition properties: export portable JSON (workflow or scheme), side-by-side compare, 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