# Support for Atlassian Jira

This page describes the Atlassian Jira data that's supported for backup and restore, including the scope at which supported data is captured and limitations or exclusions.

## Supported

### Site configuration

The following are backed up at the site level:

- Board configurations and settings
- Custom field definitions and configurations
- Field configurations and field configuration schemes
- Filters and dashboard configurations that are saved
- Group information and configurations
- Notification scheme configurations
- Permission scheme configurations
- Priorities, statuses, and resolutions
- Project role definitions and configurations
- Screens, screen schemes, and work type screen schemes
- System settings: Priorities, statuses, and resolutions
- Work item link types and configurations
- Work item security schemes and configurations
- Work type schemes and configurations
- Workflow scheme configurations
- Workflows, workflow configurations, and workflow schemes

### Space data

Component | Where the data is backed up
--- | ---
Company-managed space settings, configurations, and metadata Software Spaces: components, versions, category, lead, description Business Spaces: components, versions, category, lead, description Service Management Spaces: components, versions, category, lead, description, request types, and space organization | Individual space folders
Work items Work item metadata and settings Comments Work logs List of attachments | Individual folders

## Not supported

### Project types

Component | Considerations
--- | ---
Team-managed projects | Team-managed projects are not supported. Only company-managed projects are backed up.
Projects with '/' in the name | Not supported. Exclude these projects or remove the '/' character from the project name.

### User authentication

Component | Considerations
--- | ---
Passwords and authentication | User passwords and authentication tokens are not backed up for security reasons.
External directory integration | LDAP and SSO configurations must be reconfigured manually after a restore.

### System configuration

Component | Considerations
--- | ---
Global system settings | System-wide configurations such as mail server settings, licensing information, and application properties are not backed up.
Application links | External application links and integrations must be reconfigured manually.
Third-party apps | Custom apps, plugins, and add-ons are not backed up and must be reinstalled.
Automation rules | Automation rules are not backed up.
Jira Assets | Jira Assets data is not backed up.
Jira Product Discovery | Jira Product Discovery data is not backed up.

### Visual elements

Component | Considerations
--- | ---
Avatar images | Space and user avatar images are not included in the backup structure and must be re-uploaded manually.

### Work item relationships

Component | Considerations
--- | ---
Work item hierarchy | Work item hierarchy relationships are not backed up.
Work item links | Links between work items may not be fully restored if target work items don't exist in the destination.
Watchers | Work item watcher information is not included in the backup structure.

### Agile features

Component | Considerations
--- | ---
Board configurations | Agile board configurations, quick filters, and swimlane settings are not backed up.
Sprint data | Active sprint information and burndown charts are not backed up.

### Reporting

Component | Considerations
--- | ---
Custom reports | Custom report configurations and analytics data are not backed up.

×

Loading...