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
One practical approach to how the IT function of a global enterprise can govern strategy, manage digital products and services, and deliver work continuously, using a coherent three-layer model based on a hybrid operating model. Building on What We Already Read More
Issue migration between Jira projects can usually be handled in two ways: Same instance tendentially using Move or Bulk Move Different instances tendentially using export/import or API/script Migration Within the Same Instance Method 1 This is the simpler case. Main Read More
Customer feedback provides insights that operational metrics alone cannot capture. Jira Service Management has long offered built-in CSAT surveys, automatically collecting satisfaction ratings through a simple star-based mechanism when tickets are resolved. With the introduction of Native surveys, Atlassian extends Read More
Automation is now part of everyday operations. It helps teams move faster, cut down on manual work, and keep processes consistent. But automation only works well if it can be trusted. When something breaks in the background and nobody notices, Read More
Practical lessons learned from real-world alert routing, automation, and integrations Introduction As mentioned at the end of Part 1, let's continue exploring practical use cases and real‑world solutions for Jira Operations alert handling and enrichment. NetEye, Icinga, and Jira Ops Read More