nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Importing csv to existing project failing with invalid type and status (even though they are valid)

Samit

Hi,

So i'm doing a csv import, just one comma separated row

The relevant columns are

Issue Type, Status

Story, Done

Mapping all looks fine

Issue Type (csv) -> Work Type (Jira)

Status -> Status

And yet when i import:

Error in issue type "task" — not found in target jira project "<jira project>",Issue type task is missing in your Jira project.

Error in issue status "to do" — not found in target jira project "<jira project>",

Issue status to do is missing in your Jira project

Which is accurate since the project does not have that worktype and status. But why is it trying to map to them anyway since i have explicitly mapped to the correct (and existent) type and status

Thanks

Accepted answers

All comments

Marc -Devoteam-

Hi @Samit

If issue type Task and status TO DO is not used on workflow related to the work type mapped in the CSV these errors will occur.

You can't use work types and statuses in the CSV if they are not used in the space.

Samit

Thanks @Marc -Devoteam- - But as the original problem states, i'm not importing status of To Do , the status in the csv is Done (and far as i can see correctly mapped at the time of importing), so why is Jira trying to import it as status To do and work type of Task even though the csv is set to Story (it's essentially ignoring those 2 columns column . So essentially my question boils down to - Why is jira ignoring the mappings and what can i do to ensure it does not and imports the correct work type (Story) and status (Done) - both of which exist in the workflow?

Marc -Devoteam-

Hi @Samit

Can you provide your mapping on the import and the error log

Also what are the steps you are taking?

Samit

Piotr Mederak

Hi @Samit,

This is a frustrating one, because from what you described the CSV itself looks simple and the mapping appears to be correct: Issue Type = Story and Status = Done.

A few things I would check first:

Make sure the CSV values do not contain hidden whitespace or small typos
For example:
- Story instead of Story
- Done instead of Done
- different capitalization
- values copied from Excel or another tool with invisible characters
Check whether Jira is falling back to default values
The fact that the import tries to use Task and To Do suggests that Jira may not be accepting the values from the CSV and is falling back to project defaults somewhere in the import flow.
Verify the project configuration
Confirm that:
- Story is available in that specific project
- Done exists in the workflow used by Story
- importing directly into Done is allowed or supported in that context
Even if Done exists in the workflow, importing directly into a final status can sometimes be more sensitive than importing into the initial status and then transitioning later.
Try a minimal CSV
I would test with only:
- Summary
- Issue Type
- Status
This helps confirm whether the problem is really with issue type/status mapping, or whether another mapped field is affecting the import.

This is exactly the type of problem my app is designed to solve more safely.

For transparency: I work on an Atlassian Marketplace app called Excel to Jira Importer and Updater. It supports both Excel workbooks and CSV files, and it lets you review and correct the data before anything is written to Jira.

For cases like this, the useful part is that you can map your own source values to Jira values - for example your CSV issue types or statuses to the actual issue types and statuses available in Jira. You can also catch and fix small mistakes, typos, inconsistent names, or unexpected values before running the import.

So instead of discovering after the import that Jira used Task / To Do, you can review the planned result row by row first and see what will be created, updated, skipped, or blocked.

That said, for the built-in Jira CSV import, I would first try the minimal CSV test and check whether Jira is rejecting the Story or Done values and silently falling back to defaults.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud