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 

[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]

[Samit]

Thanks @Marc -Devoteam-  - As screenshots above, nothing too complex

[Marc -Devoteam-]

Hi @Samit 

Are there hidden rows or columns in the CSV?

Copy the rows 1 and 2 to aa new tab and export this as csv, will the import work then.

[Samit]

HI @Marc -Devoteam-  No there were no extra rows, But to be sure I created a brand new csv (same data) as well as removed any surplus columns that would not be mapped Plus made the csv headers like for like with the jira mapping fields

So every column has a corresponding Jira  field.

And same error