You can restore Atlassian Jira spaces to their current location (in place) or to a different Jira instance (out of place). You can restore data at the site level, space level, or issue level, choosing to restore either issues and site-level settings or metadata.
Caution
All space data in the destination location is overwritten by the restored data.
Restore Considerations
| Consideration | Behavior |
|---|---|
| Space metadata | In-place: Space metadata is not modified if the space exists. Out-of-place: Space metadata is not modified unless specifically selected for restore. |
| New space creation | If the space does not exist, a new space is created with the same name, key, description, and visibility as the source. |
| Space configurations | In-place: All existing workflows, custom fields, and permission schemes are replaced with restored configurations. Out-of-place: Configurations are restored as configured in the source space. |
| Missing users | Site settings related to users that exist in source but not in destination are added to failed items during restore (out-of-place only). |
| Issue icons | Issue icons are not backed up. Icons may differ after restore, but issue data remains intact. |
| Workflow schemes | Custom workflow schemes are restored successfully. If the active scheme was edited, restore saves it as a draft and you must manually publish it. |
| Workflow states | Issues are restored to their initial workflow state and do not maintain their original status in custom workflows. |
| Flagged issues | Issues that were flagged will be restored but will not be flagged after restore. |
| Work items web-links | Not currently supported. |
| Sub-tasks | Cannot restore a sub-task alone. The immediate parent must also be selected. |
| Custom issue hierarchy | Not supported. Restored as user story without parent-child links. |
| Cross-project links | Parent-child links and issue links across projects cannot be restored. |
| Missing reporter | The OAuth-authorized user becomes the reporter. A comment with the job ID and original reporter name is added. |
| Missing assignee | The default assignee setting is applied: • Unassigned: Issue restored without an assignee. • Space Owner: That user must have Assignable user permission or restore fails. A comment with the job ID and original assignee name is added. |
| Closed sprints | Issues with closed sprint associations are restored without the sprint link. A comment with the job ID and sprint name is added. |