Importing CSV file skipped required fields when validating

Question

I set up an issue type to have a required field on create, edit, and view screens. I also have this field under ScriptRunner behaviors as a required field mapped to its dedicated workflow. It works when manually creating the issue, but when importing via Issues menu "Import Issues from CSV" users are able to bypass the required field and still create issues. They don't get flagged that the required custom field is empty, yet they do when they don't have Story Points filled.

Field Configuration has it set to required. The custom field is mapped to the correct project.

The weird part is when I test it, I get the correct error message that the custom field is required.

Could someone help me troubleshoot this? What am I missing that is making the csv import bypass this required custom field? Jira version is 8.13 server

Diana Gorv · Accepted Answer

I found my own answer!

When you import issues via CSV, if you select via the dropdown menu the field name but forget to checkmark the box “Map field value” next to it, the import will still go through regardless if the field is required or not, and that’s why you’ll see that field is empty because it wasn’t mapped.

I'm guess this is a Jira bug then? Is there a way to set up a reminder to check that box before importing?