Summary

When attempting to create subtasks under standard issue types in Jira Cloud, users encounter error messages such as "Subtask is not permitted" or "Field Sprint is required".

Environment

Jira cloud

Diagnosis

You can't manually fill in the Sprint field for the Subtask issue type because it automatically inherits its value from the parent issue. Additionally, you can't access the field configuration to set this field as optional because it is a locked system field.

Cause

The issue arises due to a validator associated with the Sprint field within the Create transition in the workflow.

Solution

• Navigate to Workflow: Access the workflow associated with the subtask.
• Remove Validator: Within the workflow, look for the validators associated with Create transition and remove the validator linked to the Sprint field.
• Consider Workflow Separation: If the same workflow is used for all issue types, including standard issues requiring the Sprint field during creation, create a separate workflow tailored for subtask issue types without the Sprint field validator. This ensures subtasks can be created without encountering validation errors related to the Sprint field.