Can't create issues because of required fields in Jira Cloud

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

In Jira Cloud company-managed projects there are two ways to make a field required:

These implementations appear differently during issue creation. If a field is required by either of these methods, but is not on the create screen, users will be blocked from creating issues.

Field is required by field configuration  

When a field has been marked Required in your field configuration and that field appears on the create screen, you will see the field marked by an asterisk.

If the field is not assigned a value, or required fields have not been put on the create screen, issue creation results in the error "<field name>: <field name> is required."

Users will not be able to create issues until you proceed with one of these options:

  • You add the field to the create screen and the field is given a value
  • You remove the field requirement from the field configuration
  • You give a default value to the field (if possible for the field type)

Remove the required condition from the field configuration

Note that all changes made to a field configuration will affect all projects that use that field configuration.

To remove a field requirement from a field configuration:

  1. Go to the affected project
  2. Select Project Settings
  3. Select Issues > Fields 
  4. Select the Pencil icon next to the field configuration
  5. Search for the field identified in the error message
  6. The field will have a "Required" badge which will disappear when you select the Optional link in the Actions column
    field configuration in Jira. the custom field has a required badge in the name column. the linked text optional is highlighted in the actions column.


Sub-task error messages

The error messages look a bit different when creating subtasks. If you try to create a subtask and the required field is on the create screen,  a larger modal will pop-up prompting you to enter the required value.

If the required field is not on the create screen you will see a pop-up error with the text "We couldn't create the subtask. <Field name>: <Field name> is required."

Fields required by workflow validators

When a field is required by a workflow validator that has no custom error message configured, issue creation results in the error "Field <field name> is required."

We recommend using a custom error message in your workflow validator, which allows you to make it more descriptive for the actions your users should take.

Remove the field required validator from the workflow

Note that all changes made to a workflow will affect all projects that use that workflow.

  1. Navigate to your project
  2. Select Project settings
  3. Select Workflows
  4. Select Edit workflow for the affected issue types/workflow
  5. Select the Pencil icon next to the workflow name
  6. Select the Diagram editor and select the arrow representing the Create transition
  7. Select Validators as seen here:
    workflow editor with the create transition selected. a box with options for properties, validators, and post functions appears. the validators link is highlighted.
  8. For the field required validator, select the cross icon to delete it as displayed below:
    create transition editor. the validators appear at the bottom in a list. the cross icon is highlighted for the field required vaildator.
  9. Select Publish draft


Last modified on Mar 25, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.