TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including projects, issues, configurations, and attachments. However,deleted issues(Option C) cannot be imported, as they are not included in standard Jira Cloud backups or export data.
* Explanation of the Correct Answer (Option C):
* Deleted issuesare permanently removed from Jira Cloud and are not included in backups or export files created for migration. TheImport Jira Cloudfeature only imports data that exists in the source site's backup, which excludes issues that have been deleted.
* Exact Extract from Documentation:
Import Jira Cloud data
TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including:
* Projects (company-managed and team-managed).
* Issues, comments, and attachments.
* Configurations (e.g., custom fields, workflows, automation rules).Limitations:
* Deleted issues are not included in backups or exports and cannot be imported.To import:
* Create a backup from the source site inSettings > System > Backup manager.
* UseSettings > System > Import Jira Cloudon the target site.Note: Requires Jira administrator permissions and may involve Atlassian support for full migrations.(Source:
Atlassian Support Documentation, "Import data to Jira Cloud")
* Why This Fits:Deleted issuesare not part of the data exported from the source site, making them impossible to import, so Option C is the correct answer.
* Why Other Options Are Incorrect:
* Automation rules (Option A):
* Automation rulesare included in Jira Cloud backups and can be imported to the target site using theImport Jira Cloudfeature, provided they are compatible with the target site's configuration.
* Extract from Documentation:
Automation rules are included in Jira Cloud backups and can be imported, though some rules may require reconfiguration if dependencies (e.g., custom fields) differ.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Custom fields (Option B):
* Custom fieldsare part of the configuration data in a Jira Cloud backup and are imported to the target site. Their contexts and options are preserved during migration.
* Extract from Documentation:
Custom fields, including their configurations and contexts, are included in backups and imported to the target site.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Team-managed projects (Option D):
* Team-managed projectsare fully supported in Jira Cloud backups and can be imported to the target site, including their issues, configurations, and settings.
* Extract from Documentation:
Both company-managed and team-managed projects are included in Jira Cloud backups and can be imported to another site.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Attachments (Option E):
* Attachments(media files) are included in Jira Cloud backups and can be imported to the target site, provided the backup includes media data.
* Extract from Documentation:
Attachments are included in Jira Cloud backups and imported to the target site if media import is enabled.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Additional Notes:
* TheImport Jira Cloudfeature is accessed viaSettings > System > Import Jira Cloudand typically requiresJira administratorprivileges, with possible Atlassian support for full migrations.
* Deleted issues are permanently removed and cannot be recovered unless a backup from before deletion is available, but even then, they are not part of standard exports.
* Other data (e.g., automation rules, custom fields) may require post-import reconfiguration if there are incompatibilities between sites.
:
Atlassian Support Documentation:Import data to Jira Cloud
Atlassian Support Documentation:Back up Jira Cloud data