From which three sources can the Jira import wizard import data? (Choose three.)
Microsoft Excel
Trello
Bitbucket
GitHub
JSON
CSV
The Answer Is:
B, E, FExplanation:
The Jira import wizard in Jira Software Cloud allows administrators to import data from various external sources to create or update issues, projects, and other entities. The supported sources includeTrello,JSON, andCSV, making these the correct choices.
Explanation of the Correct Answers:
Trello (Option B):
The Jira import wizard supports importing data from Trello boards, including cards, lists, and users, into Jira projects. This is useful for migrating Trello projects to Jira.
Exact Extract from Documentation:
Import data from Trello
The Jira import wizard allows you to import Trello boards into Jira Cloud. You can import cards as issues, lists as statuses, and map Trello users to Jira users.
To import:
Go toSettings > System > External System Import.
SelectTrelloand authenticate with your Trello account.
Follow the wizard to map data and import.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
Why This Fits: Trello is a supported source for the Jira import wizard, making it a correct choice.
JSON (Option E):
The Jira import wizard supports importing data from a JSON file, which can include issues, projects, and configurations. This is useful for advanced users or migrations from other systems that can export JSON.
Exact Extract from Documentation:
Import data from JSON
You can import issues and other data into Jira Cloud using a JSON file. The JSON format must follow Jira’s import schema.
To import:
Go toSettings > System > External System Import.
SelectJSONand upload the JSON file.
Map fields and configurations as prompted.Note: JSON imports are useful for custom migrations or backups.(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
Why This Fits: JSON is a supported format for the Jira import wizard, making it a correct choice.
CSV (Option F):
The Jira import wizard supports importing data from CSV files, which can include issues, users, and other data. CSV imports are commonly used for bulk issue creation or migration from other systems.
Exact Extract from Documentation:
Import data from CSV
The CSV importer allows you to import issues, users, and other data into Jira Cloud from a CSV file.
To import:
Go toSettings > System > External System Import.
SelectCSVand upload the file.
Map CSV columns to Jira fields and configure settings.Note: Ensure the CSV file is properly formatted to avoid errors.(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
Why This Fits: CSV is a supported format for the Jira import wizard, making it a correct choice.
Why Other Options Are Incorrect:
Microsoft Excel (Option A):
The Jira import wizard does not directly support Microsoft Excel files (.xlsx, .xls). To import Excel data, it must first be converted to CSV format.
Extract from Documentation:
Jira does not support direct imports from Excel files. Save Excel files as CSV and use the CSV importer to bring data into Jira.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
Bitbucket (Option C):
Bitbucket is not a supported source for the Jira import wizard. While Bitbucket integrates with Jira for development workflows (e.g., commits, pull requests), it does not provide issue or project data for import.
Extract from Documentation:
Bitbucket integrates with Jira for development tools but is not a source for the Jira import wizard.
(Source: Atlassian Support Documentation, "Integrate Jira with Bitbucket")
GitHub (Option D):
GitHub is not a supported source for the Jira import wizard. While GitHub can integrate with Jira for development workflows, importing issues or projects from GitHub requires third-party apps or manual export to CSV/JSON.
Extract from Documentation:
GitHub is not supported by the Jira import wizard. Use third-party apps or export GitHub data to CSV or JSON for import.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
Additional Notes:
The Jira import wizard is accessed viaSettings > System > External System Importand requiresJira administratorprivileges.
Other supported sources (not listed in the options) include Jira Server/Data Center, Asana, and Monday.com, but Trello, JSON, and CSV are the correct matches here.
Your organization has two Cloud sites. You will use the "Import Jira Cloud" feature to migrate from one Jira site to the other. What can you not import?
Automation rules
Custom fields
Deleted issues
Team-managed projects
Attachments
The Answer Is:
CExplanation:
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.
