Data Management, Import/Export, and Integrity
Moving and protecting data
Data management covers import/export, backup, and integrity checks. Jira supports CSV import (with field mapping), JSON backup restore, and project import from other trackers. Export options include CSV export of search results and full XML/JSON backups. Candidates must know that a backup includes attachments only if configured, and that restoring a backup replaces data rather than merging it.
Integrity concerns the index: search results depend on the index, and a reindex is the standard fix for issues that do not appear in JQL results or fields that seem stale. The integrity checker validates configuration consistency (for example, schemes referencing missing objects).
Traps to watch
- Assuming a CSV import preserves history, comments, or attachments; it generally does not.
- Forgetting that field mapping during import requires the target field to exist and be on the relevant screens.
- Confusing a reindex (search correctness) with a backup (data preservation).
- Overlooking that restoring a backup can overwrite newer data.
Rule of thumb
If search behaves oddly but the data looks correct in the UI, reindex first. If data is missing entirely, check the import mapping and whether the field was on the create screen.
Worked example: imported issues are missing a custom field value. The CSV column was mapped to a field not present on the target project's create screen, so the value was dropped. Add the field to the screen and re-import.