A rollback plan is only credible after a controlled exercise proves what can be restored, what must be rebuilt, and who is authorized to make the production decision. Project platforms often divide information among core records, attachments, automation, marketplace apps, identity systems, and external file stores. The test must cover those boundaries.
Define the failure scenario
Choose one realistic event, such as a workflow configuration error, accidental project deletion, permission change, failed integration update, or broad import mistake. State the recovery objective: the maximum tolerable data age, expected restoration time, and the functions that must work before users return. Name the test owner, observers, and person authorized to stop the exercise.
Use a sandbox or other isolated environment. Do not test by overwriting live data. Atlassian describes sandboxes as environments for experimentation and testing before changes reach production. Source: https://support.atlassian.com/organization-administration/docs/manage-atlassian-sandboxes/
Inventory the rollback package
List the dated backup or export, attachment set, workflow and field configuration, automation definitions, app configuration, integration credentials location, user and group mapping, permissions, project identifiers, and validation checklist. Record a cryptographic hash or other integrity reference when the organization's process supports it. Confirm that the people running the test can access the package without depending on the failed platform.
Backup scope matters. Atlassian says its Jira Cloud export includes many core records but excludes categories such as automation rules and third-party app data, with automation available through a separate export. Source: https://support.atlassian.com/jira-cloud-administration/docs/export-issues/
Restore into an empty test destination
Document every step, start time, warning, and manual decision. Atlassian's backup-and-restore FAQ says a backup can be restored into an empty sandbox, that backups in Atlassian-owned storage expire after 30 days, and that Marketplace app data is not supported. It also says selective project or space restoration is not available through that backup system. Source: https://support.atlassian.com/organization-administration/docs/backup-and-restore-frequently-asked-questions/
Those constraints mean the exercise should verify the exact subscription and tools in use. If a platform provides only whole-environment restoration, a small configuration mistake may need a configuration-level reversal rather than a broad data restore. Record that distinction in the decision tree.
Validate data and behavior
Use a prepared sample containing open and closed work, custom fields, comments, attachments, linked items, several roles, an automation, and an integration. After restoration, compare counts and identifiers, then test search, permissions, notifications, automation, attachments, reports, and linked systems. Do not reconnect production integrations until the restored environment is confirmed isolated and safe.
Review audit evidence for the simulated change and the reversal. Jira's audit documentation says the log covers many configuration events but is not intended to capture every activity. Source: https://support.atlassian.com/jira-cloud-administration/docs/audit-activities-in-jira-applications/ The test record should therefore include its own timestamps and operator notes.
Conduct the go-or-no-go review
A successful exercise meets the declared data-age and time objectives and passes every critical validation. If attachments, app data, automation, or permissions require manual reconstruction, measure that work and update the estimate. Record any irreversible gap. Do not call the exercise successful because an import completed.
Close with the backup used, destination, elapsed time, verified functions, failed checks, missing scope, corrective actions, and next test date. The result should tell an incident lead whether to reverse one setting, restore an environment, or continue forward with a fix. That decision clarity is the real product of the exercise.
Sources
- Test and explore with Atlassian sandboxes — Atlassian
- Export data from Jira Cloud — Atlassian Support
- Backup and restore frequently asked questions — Atlassian
- Audit activities in Jira — Atlassian Support