Hi,
I have created a new workflow scheme and want to replace with the exsiting workflow schdme. Let me know how can i take the backup so to ensure if anything goes wrong i can restore the previous data.
Hi, you can create a copy of the workflow scheme and all its workflows, however if statuses have been changed and during the migration you've mapped workflow statuses, there may be loss of data. In that case I suggest doing a full backup and restore if required. You'd probably need to "freeze" the system in case.
Thanks
Actually when i assign the new workflow scheme to an existing Project it says that please ask your system administrator to take a backup in xml file. How can i take that back up.
Hi, you can do an export by following: https://confluence.atlassian.com/display/AOD/Exporting+issues. You will need to be an admin to do this.
Will this take back up of the entire project configured in JIRA?
I want to take a backup of only one project.
Necro-posting since this thread still surfaces for the "backup before a workflow scheme change" question, and the underlying gap Harry's describing hasn't really gone away — just moved. This was Server/on-premise Jira in 2012 (XML export, full-instance backups only), but the same "no official way to snapshot just one project's config" limitation exists in Jira Cloud today too, just for different reasons: there's no native scheduled snapshot of a project's workflow/permission scheme config that you can diff against or restore from before making a scoped change.
The safest practical approach for anyone landing here now: before reassigning a workflow scheme, manually document the current scheme's config (screenshots or exported JSON via the API) so you have something to compare against if the migration causes unexpected status mapping issues. It's not a real backup, but it's better than nothing, and it's basically the same workaround people have been using for over a decade because the native tooling doesn't offer a cleaner option.
Hi — you’re right that Cloud still doesn’t give a clean “export file → import on another site” path like Data Center XML. Company-managed workflows can be exported, but native import is Marketplace-only or API work. Remapping statuses and third-party rules is the hard part. For Cloud company-managed workflows I built Easy Workflows for Jira: export/import as JSON, a read-only validate step before anything changes, side-by-side compare, plus snapshots and one-click restore. Data stays in the site (Forge). Try free (30 days; free forever for ≤10 users, then about USD 2/user/mo): https://marketplace.atlassian.com/apps/503324296/try?hosting=cloud It does not move issues, team-managed workflows, or DC XML. For whole projects, use Atlassian Copy product data. Questions: info@berkly.nl
It looks like you're new here. Sign in or register to get started.
