Guide · Jira Cloud
Jira Cloud workflow change history / audit trail
When someone asks who changed this workflow, native Jira Cloud does not give you a clean, workflow-scoped trail. Easy Workflows records every export, import, snapshot, and restore in an in-site audit history so you can see who changed what — and restore when needed. Company-managed only. Free for teams ≤10.
30-day trial · Free for teams ≤10 · then about USD 2/user/mo
Related: restore from snapshot Related: validate before import Related: backup / keep snapshots Related: compare before promote Easy Workflows app page01 — The gap
Native Cloud does not answer “who changed this workflow?”
Jira’s site-wide audit log is broad and not built as a workflow definition history. After a sandbox promote, a hand-edit on production, or a Marketplace import, admins still ask: who wrote the last change, what did they change, and can we get the previous definition back? Chat threads and screenshots are not an audit trail.
02 — What the trail records
Exports, imports, snapshots, restores — in the site
- Who — the Jira admin that ran the action (export, import, snapshot, restore).
- What — which company-managed workflow (or scheme package) was touched.
- When — timestamp of the lifecycle event.
- Linked snapshots — before a write, Easy Workflows keeps the previous definition so history connects to one-click restore.
History stays on Atlassian Forge with your site — definitions and the trail are not stored on external Berkly servers.
03 — When you need this page
Compliance review, incident, admin handoff
- Compliance / change review — show that workflow changes were validated and recorded, not “someone clicked Publish.”
- Incident — production broke after a change; use the trail to identify the last import/restore, then restore a known-good snapshot.
- Admin handoff — a new owner needs a readable history of sandbox→prod moves without digging through email.
04 — Safe habit with the trail
Validate → snapshot → write → trail already has it
- Validate read-only until Ready (validate guide) — do not write blind.
- Snapshot (manual, or rely on the pre-write snapshot) so restore has a target (backup).
- Import / promote / restore — the action is recorded on the audit trail.
- Review — open the trail when asked who changed what; restore if the write was wrong.
05 — Not these other guides
Audit trail vs restore vs validate vs move
- This guide — who changed what (lifecycle history / compliance view).
- Restore — pick a snapshot → one-click restore → verify (the recovery action the trail points at).
- Validate — Ready / blocking before any write.
- Backup — how to keep daily/manual snapshots.
- Rollback — incident path after a bad import.
- Move / export-import / compare / scheme promote — how to change definitions; this page is the record of those changes.
06 — Scope (honesty)
Company-managed · Forge · not Jira’s global audit log
This path is for company-managed Jira Cloud workflow lifecycle events in Easy Workflows (export, import, snapshot, restore). It is not team-managed, not Data Center XML, not a replacement for Jira’s site-wide audit log for every admin setting, and not issue/project history. Free for teams ≤10; 30-day trial; then about USD 2/user/mo via Atlassian. We do not claim mid/large seat pricing cheaper than Workflow Wizard — pick the tool that matches the job.
07 — Tooling
Easy Workflows for Jira
Easy Workflows for Jira is a Forge app with a full audit trail of every export, import, snapshot, and restore — plus side-by-side compare, read-only validate with a Ready / blocking verdict, and in-site one-click restore.
Marketplace: Easy Workflows for Jira. Support: info@berkly.nl.