In Jira Cloud, you can set a default for a text custom field through its field context. If users must be able to leave a field unanswered, keep it optional and do not preselect a choice. For fields with predefined options, Atlassian documents editing the options available in a context, but its cited Cloud instructions do not describe a select-list default control in the same way they describe a text-field default.
First, distinguish an empty field from an option called “None”
An empty field has no value. A select-list option named “None” is a selected value that may be stored, searched, or reported like any other answer. Use a literal option such as “None” or “Not applicable” only when that is the meaning you want recorded—not as a substitute for leaving the field blank.
As an Amazon Associate I earn from qualifying purchases.
Atlassian’s guidance for making a select-list field visible when its value is “None” is explicitly for Jira Data Center, not Jira Cloud. Do not apply that workaround as a Cloud procedure. Atlassian’s Data Center-only guidance describes that distinction.
Set a Jira Cloud field default in its context
- Find the field. Open Settings > Work items > Fields, locate the custom field, and check its type and contexts.
- Open the context settings. From the field’s More actions menu, select Contexts and default value, then edit the context you intend to change. See Atlassian’s context configuration instructions.
- Choose the control for the field type. For a text field, Atlassian documents Edit Default Value; the configured text automatically populates the box when a work item is created. For a field with predefined choices, the documented control is Edit Options, which changes the choices available in that context. The cited Cloud documentation does not describe a select-list default control in the same way as the text-field default.
- Keep the field optional if blank is valid. Do not assign a preselected choice if users need to submit the field with no value. If the field is required, users cannot leave it blank.
- Review the context scope before saving. A context applies to the spaces and work types included in its configuration. Jira fields have a default context covering all spaces and work types unless the configuration is scoped differently. Choose the narrowest appropriate context and verify which work items it covers. See Atlassian’s explanation of field context scope and what contexts do.
Verify what users will see
After saving, open the work-item creation experience for a space and work type covered by the context. Check that the field begins in the intended state, that users can leave it blank when that is allowed, and that creation works both with a blank field and with a selected value. This is an administrator validation step; the result depends on the field configuration and applicable context.
#1 Best Overall
Troubleshoot creation errors tied to contexts or defaults
A required select field has no available choices
Check which context applies to the space and work type where creation fails. Atlassian identifies a context with no configured options as one cause of an issue-creation error. The documented remedies are to switch to a context with values or add the necessary options to the active context. Atlassian’s troubleshooting article was updated September 25, 2025.
Creation reports an invalid or missing default
Use the browser developer console to identify the field named in the error response, then inspect that field’s context and default. A hidden field can still block creation, so also check hidden fields in the relevant field configuration. Correct or clear an invalid value, then retry creation for the same space and work type. Atlassian’s Jira Cloud troubleshooting guidance was updated September 17, 2026.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
