CSV import fails with InvalidInputException Error Due to Issue Type and Validator Conflict
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
This article addresses the InvalidInputException
error encountered in Jira when attempting to process issues while importing a CSV file. The error message indicates that the issue type 'Production Incident' is not supported due to a validator rule conflict.
- Error Message: InvalidInputException: [Error map: [{}]] [Error list: [[Please Select a valid Request Type from the list. Issue type 'Production Incident' is not supported]]
Environment
Jira Service Management Cloud
Diagnosis
The error is triggered by a validator rule in the workflow associated with the 'Production Incident' issue type. The backend logs show the error as follows:
InvalidInputException: [Error map: [{}]] [Error list: [[Please Select a valid Request Type from the list. Issue type 'Production Incident' is not supported]]
In the current configuration, the '<TEST>' issue type is mapped to a workflow validator that checks for the presence of a "Request Type" field value. Since '<TEST>' does not have a corresponding "Request Type", the validator fails, leading to the error.
Cause
The issue arises because the validator rule in the workflow expects a "Request Type" field, which is not applicable to the '<TEST>' issue type. This mismatch results in the error message indicating that the issue type is not supported.
Solution
To resolve this issue, you can choose one of the following solutions:
Remove the Validator:
- Navigate to the workflow configuration and locate the validator associated with the '<TEST>' issue type.
- Remove the validator that checks for the "Request Type" field.
Create Another Issue Type:
- Create an additional issue type for the project.
- During the CSV import process, map only the "Summary" field and select "Do not map this field" for all other fields. This avoids the conflict with the "Request Type" field.
For further assistance, please consult the Jira documentation or contact support.