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
A quick overview of the new native numerical calculation feature available in Jira systems: something we have been waiting for a long time. Introduction The ability to perform calculations within an integrated management system is one of the most requested Read More
Introduction Managing a service desk is usually straightforward when the team is small. A request comes in, someone picks it up, and the work gets done. Things become more complicated when the service desk grows. Different teams start supporting different Read More
Why shared devices need dedicated governance Not every IT asset is assigned to an individual employee. Monitors, docking stations, meeting-room equipment, printers and other devices are often shared across an office or location. Although these assets have no individual owner, Read More
In my previous posts of this series, we explored how to handle, filter, route, and enrich alerts generated by NetEye and forwarded to Jira Operations: https://www.neteye-blog.com/blog/2026/03/25/jira-operations-tips-tricks-for-neteye-users-part-1/ https://www.neteye-blog.com/blog/2026/06/15/jira-operations-tips-tricks-for-neteye-users-part-2/ In this article, I'll show you how we automated the creation of customer Read More
When you have a large request, it's tempting to turn every step into a sub-task. It makes sense: Each activity is visible, assignable, and trackable. However, there is a downside. Projects can quickly become crowded with work items, navigation becomes Read More