Ready to transfer your projects from another tool to Jira? Here’s how to do it quickly and easily:
1.Prepare your file: Organize your data in a format that Jira recognizes, such as a CSV file. Make sure the fields match those in Jira (title, description, etc.). Here’s an example of what the file should look like:
2.Configure the import: In Jira, select the import option, choose your file and select the project to which you want to import data.
The most important part of the configuration is the mapping of the fields in your file to the corresponding fields in Jira.
⚠Remember that assignees and reporters (the same goes for watchers) will only be imported if they are identified by the ID. If you have this information in your file, remember to map it this way:
🧙♀️ AssigneeID -> Assignee
🧙♂️ ReporterID-> Reporter
If there are e.g. Epics and Subtasks in the file, then in order not to lose the parent-child relationship between Epics and Task and between Task and Subtask, you must remember to map the Issue ID, Issue Type and Parent fields.
Start the import: once the fields are correctly mapped, click “Import” and wait a few moments.
Verify the result: check that everything has been imported correctly, and resolve any issues.
Extra tips for a flawless import
Create a test project: before carrying out the import on a project in production, I recommend that you carry out a test project
Divide the import: if you have a lot of data, divide it into smaller chunks
Consult the official documentation: you’ll find specific details for your Jira version
Custom fields: make sure they match perfectly
Relationships: if there are links between your data, verify they are imported correctly
Attachments: check the size and format limitations
In the world of customer support, efficiency is key. And what could be more efficient than a system that allows customers to find answers on their own and agents to solve problems in record time? The answer is the integration Read More
As discussed in my previous posts (Part 1 and Part 2) on managing Alerts with Jira Service Management, the way JSM handles alerts is crucial for keeping IT operations smooth. But what happens when an alert pops up at 3 Read More
Managing user access in Atlassian Cloud can become complex, especially when integrating with Identity Providers (IDPs) for user provisioning via SCIM (System for Cross-domain Identity Management). A common challenge arises when users who were initially synchronized through your IDP become Read More
A brief introduction to Whiteboards, a new tool that facilitates a new form of collaboration between people. Why are we still talking about the documentation problem? In my previous post, we discussed the challenging topic of documentation management within a Read More
Have you always found Portal Groups in Jira Service Management (JSM) to be useful for organizing and triaging requests, but noticed they couldn’t be used to filter issues? Atlassian has addressed this limitation with a new categorization feature called "Request Read More