Import Tasks into Jira: A Step-by-Step Guide Using CSVs
Need to import tasks into Jira without cleanup? This Jira import tasks guide covers CSV setup, field mapping, and common errors. Read now to import with confidence.
Moving tasks into Jira through a CSV can save hours, especially when a team is switching systems or consolidating work. But a small mismatch in columns, dates, or issue types can turn a quick import into a cleanup project. Duplicate tasks, missing assignees, and broken parent-child relationships can make the new project harder to use than the old one.
But here's the truth: a smooth import starts before you open Jira. Prepare a clean CSV, map each column to the right Jira field, and test a small batch before importing everything. This guide walks you through each step, explains common errors, and shows you how to check the results. You’ll know what to prepare, where to start, and how to avoid preventable rework.
How to import tasks into Jira from a CSV
To import tasks, prepare a CSV with clear headers, open Jira’s external system import tool, map the columns, and validate a small test import. You may need Jira administrator permissions, and menu names can vary slightly by Jira version.
-
Prepare the task information. Choose the project where the tasks should appear, then gather the fields you want to import. Common fields include Summary, Description, Issue Type, Priority, Assignee, Reporter, Due Date, and Labels.
Use one row per task and keep each column focused on one type of information. For example, put a task’s title in Summary and its longer explanation in Description.
-
Create and check your CSV. Save the task list as a comma-separated values CSV with a header row. Make sure every row has a Summary and an Issue Type, and remove blank rows or accidental duplicate tasks.
Use a consistent date format, such as 2025-03-14, and check that commas or quotation marks inside descriptions are handled correctly. If names contain special characters, save the CSV using UTF-8 encoding.
-
Open Jira’s import tool. In Jira, go to Settings > System > External system import, then choose the CSV import option. You may see a different menu path if your Jira version or permissions differ.
Choose the destination project and provide the CSV when prompted. If you cannot access the import option, ask a Jira administrator to grant the required permission or run the import.
-
Map CSV columns to Jira fields. Jira asks you to match each column header with a Jira field. Map Task Name to Summary, for example, and match your priority or due-date columns to their corresponding fields.
Do not map a column just because its name looks similar. Check that the values fit the Jira field type. A date column should map to a date field, while a list of labels should use Jira’s expected separators.
-
Review project and issue settings. Confirm the target project, issue types, date format, and any required field values. Jira may ask you to match names from the CSV to existing Jira users or values.
For parent-child tasks, check which hierarchy fields your Jira version supports. If you are importing subtasks or parent relationships, test them with a small sample before attempting the full set.
-
Run a small test import. Import a handful of representative tasks first. Include examples with long descriptions, labels, assignees, due dates, and any hierarchy you plan to use.
Open the resulting Jira issues and confirm that the values landed in the intended fields. If anything is missing or misformatted, fix the CSV or mapping before continuing.
-
Import the remaining tasks and verify them. Once the test looks right, repeat the import with the complete set. Check the import summary for errors, then review several tasks in Jira.
Confirm that task counts, key fields, and project placement make sense. Keep the original task list available until the team has checked the imported work.

Prepare your CSV so Jira can read it cleanly
Jira’s importer depends on consistent headers and values. A column called Task Name can still map to Summary, but clear headers such as Summary, Issue Type, and Priority make the mapping easier to review.
Keep a simple task list with one row per issue. For example, a row might contain “Review onboarding emails” as its Summary, “Task” as its Issue Type, “Maya Chen” as Assignee, and “High” as Priority.
Here's why: consistent values prevent avoidable mismatches. If the priority column contains “High,” “high,” and “H,” Jira may not treat those entries as the same value. Standardize names and formats before importing.
Useful columns for a basic task import
- Summary: A short, specific task name.
- Description: Context, acceptance criteria, or instructions.
- Issue Type: The Jira issue type, such as Task or Bug.
- Priority: A priority value available in the destination project.
- Assignee: A Jira user who can be matched during import.
- Due Date: A consistently formatted date.
- Labels: One or more searchable tags.
You do not need every column for every project. Start with the fields your team will use, then add optional details only after checking that Jira can map them correctly.
Map fields and preserve task relationships
Field mapping tells Jira where each CSV value belongs. If you map a task’s title to Description instead of Summary, the import may complete successfully while leaving issues difficult to scan. Review every mapping before proceeding.
Some values must match existing Jira settings. A project may accept only certain issue types, priorities, or user accounts. If an assignee name does not match a Jira account, the task may import without the expected assignee.
Handle parent tasks and subtasks carefully
Task hierarchies need extra attention because parent-child fields and import behavior can differ across Jira versions. Where supported, use the required identifiers or parent fields and follow Jira’s prompts for linking related issues.
For example, test one parent task with two subtasks before importing a full project plan. Check the resulting issue pages to confirm that both subtasks appear under the intended parent, rather than as unrelated tasks.
Decide how to handle users and custom fields
Check that assignees and reporters already have Jira accounts and that their identifiers match what Jira expects. If a person cannot be matched, agree on a fallback before importing, such as leaving the task unassigned.
Custom fields can also require configuration. If the destination project uses a field such as “Request Type,” confirm that it exists and accepts the values in your CSV. Otherwise, leave it unmapped or prepare the project first.
Run a test import and validate the results
A test import helps catch mapping mistakes while they are still easy to fix. Select a small sample that represents the different task types and field values in the full import, rather than testing only simple rows.
The best part? You can check the actual Jira issues before committing to the larger import. Compare the Summary, Description, assignee, priority, labels, and dates with the corresponding task entries.
Use a practical validation checklist
- Confirm that the imported task count matches the sample size.
- Check that each task appears in the intended project and issue type.
- Verify that date values and special characters display correctly.
- Review a task with labels, an assignee, and a long description.
- Check parent-child relationships and issue links, if included.
- Review Jira’s import results for skipped rows or field errors.
If something is wrong, pause before importing the full set. Correct the field mapping or CSV values, then run another small test. This is usually faster than correcting dozens of issues afterward.
Common CSV import errors and how to fix them
Most import problems come down to mismatched values, missing required fields, or inconsistent formatting. Jira’s error details can point you toward the affected row or field, so review the results rather than assuming that a completed import means every task is correct.
Tasks import without assignees
Why it happens: The name or account identifier in the CSV does not match a Jira account, or the account cannot be assigned in the destination project.
How to fix it: Confirm the correct Jira identifiers and permissions. If you cannot resolve every account before importing, leave those tasks unassigned and assign them after the import.
Dates appear wrong or fail validation
Why it happens: The CSV uses a date format Jira does not expect, or the import settings use a different format from the values in the column.
How to fix it: Standardize dates throughout the CSV and select the matching format in the import settings. Test a row with a due date and inspect the resulting Jira issue.
Some rows are skipped
Why it happens: A row may lack a required field, contain an invalid issue type, or include a value that does not match the project’s configuration.
How to fix it: Read the import error details, correct the affected values, and retry the relevant tasks. Keep a record of what imported successfully to avoid creating duplicates during a second attempt.
Parent-child links are missing
Why it happens: The hierarchy fields may not be mapped correctly, the identifiers may not match, or the selected import method may not support the relationship as expected.
How to fix it: Check Jira’s supported hierarchy fields for your version and run another focused test. If necessary, import the parent tasks first and add subtasks afterward.
When another project platform may fit better: ONES.com
Value proposition: ONES.com brings project management and knowledge management together, with ONES Project for project work and ONES Wiki for knowledge management. They are sold separately, so a team can choose the capability it needs.

If importing tasks highlights a broader need to change platforms, ONES Project is a Jira alternative with Jira-compatible workflows. You can evaluate it for teams that want project workflows, reporting, and deployment choices without relying on as many plugins.
Core capabilities
- Repeated plugin maintenance slows teams down: ONES Project provides built-in project capabilities, which can reduce reliance on add-ons for common workflows.
- Existing Jira processes are difficult to replace: Jira-compatible workflows help teams carry familiar process patterns into a new project environment.
- Teams need different review paths: Custom workflows let a team shape task stages around its own approvals and handoffs.
- Standard fields do not capture enough detail: Custom fields provide places to record project-specific information within the workflow.
- Sprint planning needs a consistent home: Sprint management supports teams organizing and tracking iterative work.
- Manual repeat actions take time: Automation can handle configured workflow actions and reduce routine updates.
- Project progress is hard to inspect: Built-in reporting gives teams a way to review project status and work progress.
- Hosting requirements limit cloud adoption: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
- Self-hosting raises feature concerns: Cloud and self-hosted versions have full feature parity, helping teams assess deployment based on operating needs.
Application scenarios
A team reviewing its Jira setup: If a CSV migration is part of a broader platform review, the team can assess ONES Project’s workflows, fields, sprint management, and reporting against its daily requirements. A small trial project can help check whether the working process fits.
An organization with restricted network requirements: A team that cannot use a public cloud service can evaluate ONES.com’s On-Premise, Private Cloud, or Air-gapped deployment options. It can compare those choices with its security and operating requirements.
ONES.com offers a free plan for up to 30 seats. Teams can assess ONES Project as a Jira alternative and consider ONES Wiki separately if they also need knowledge management.
Common challenges when importing Jira tasks
- Challenge: The CSV has inconsistent field values. Solution: Standardize labels, priorities, issue types, and user identifiers before importing. For example, choose one spelling for each priority instead of mixing abbreviations and full names.
- Challenge: The import requires permissions you do not have. Solution: Ask a Jira administrator to run the import or provide the required access. Confirm permission before preparing a large task list.
- Challenge: A second import could create duplicates. Solution: Track which rows imported and review Jira’s results before retrying. Correct only failed tasks where possible instead of repeating the entire import.
- Challenge: The task hierarchy is more complex than expected. Solution: Test representative parent tasks, subtasks, and links first. Import in a deliberate order if your Jira version requires parent issues to exist before their children.
FAQs about importing tasks into Jira
Do I need Jira administrator access to import tasks?
You may need Jira administrator permissions to access the external system import tool. Permission requirements can vary by Jira version and configuration. If you cannot find the CSV import option, ask a Jira administrator to confirm your access or run the import. It is also helpful to check permissions before preparing a large task list, so access issues do not delay the migration.
Which columns are required for a Jira task import?
At minimum, each task needs a Summary, and Jira generally needs an Issue Type to create the issue correctly. Other requirements depend on your project configuration. A project may require additional fields, such as a team-specific category or component. Start with the required fields, then add assignees, descriptions, labels, and dates after confirming that Jira can map them.
Can I import subtasks and parent relationships from a CSV?
Jira supports hierarchy-related import options in some configurations, but the exact fields and behavior can vary by version. Check the fields Jira offers during import and follow its guidance for parent identifiers or hierarchy mapping. Test one parent with a few subtasks first. After importing, open the issues and confirm that Jira displays the intended relationships.
What should I do if Jira cannot match an assignee?
First, confirm that the person has an active Jira account and that the CSV contains the identifier Jira expects. Display names may not always be sufficient. Check that the person can be assigned work in the destination project. If the account cannot be matched in time, import the task without an assignee and assign it manually after the task appears in Jira.
How can I avoid duplicate tasks during a retry?
Review Jira’s import results and note which rows succeeded before running another import. If only a few rows failed, correct and retry those tasks rather than submitting the entire CSV again. If you need to repeat the full import, confirm how Jira identifies existing issues and consider removing the previously imported sample from your retry set.
Conclusion
A reliable Jira CSV import starts with a clean task list, consistent values, and careful field mapping. Test representative tasks first, inspect the resulting issues, and correct any problems before importing the full set.
That small amount of preparation can prevent hours of cleanup later. If the import is part of a wider project-management change, compare the workflows, reporting, hosting, and administration your team needs before choosing its next step.