First decide whether you need a field left blank or a selectable option whose label is None. They are different: a blank value is represented as null when clearing a select-list field, while a literal None option must be added to the custom field’s option list. For a Jira-created custom field, an administrator can recreate that option in the correct field context with Jira Cloud’s REST API.
Choose the right meaning of “None”
- Blank field: The issue has no selected value. To clear a select-list value, Atlassian’s REST example uses
null; it does not create a selectable option. See Atlassian’s instructions for setting a select-list value to None. - Literal option: Users should see and be able to select the text
None. Recreate it as an option in the affected custom field’s applicable context.
Jira’s JQL examples also distinguish an empty tier, written as none in the relevant query context, from literal text such as "none". See Atlassian’s Jira Cloud JQL functions documentation.
As an Amazon Associate I earn from qualifying purchases.
Identify the field and its context
Before adding an option, establish the custom field’s ID, the context ID that applies to the relevant project and issue types, its field type, and who owns the field. Jira’s custom field option resource covers checkboxes, radio buttons, single- and multiple-choice select lists, and cascading select fields. Context matters: an option added to a different context may not appear where users expect it.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Inspect the existing options for that context before making a change. Atlassian’s Jira Cloud REST API v3 documentation for issue custom field options describes retrieving a paginated option list as well as creating, updating, ordering, and deleting options.
#1 Best Overall
Recreate a Jira-created option with the Cloud REST API
- Confirm permission. The option-management operations require the global
Administer Jirapermission. - Confirm ownership. Use this route for a Jira-created custom field. If a Connect app created the field or its options, use the separate app options resource documented by Atlassian rather than the Jira-created field-option endpoint.
- Check the field and context. Find the correct
fieldIdandcontextId, then review the options in that context so you do not add a duplicate or place the replacement in the wrong scope. - Create the option. Send a
POSTrequest to/rest/api/3/field/{fieldId}/context/{contextId}/option, supplying the option labelNonein the request body. Follow the request schema in Atlassian’s API documentation. For a cascading select, the endpoint also supports cascading options. - Verify availability. Retrieve the context’s options again and confirm the replacement appears there. Then check that the intended project and issue types use that context.
Atlassian documents a maximum of 1,000 options per request and 10,000 options per field. These are API product limits; they are not a recommendation to approach either limit.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When the field should be blank instead
Do not add a literal choice if the goal is simply to remove an issue’s current selection. Edit the issue using the appropriate field-edit behavior, or use the relevant REST operation with a null field value. A blank value and an option labeled None have different effects: the former leaves the field unset, while the latter is a value a user can select.
Quick Recap
Cloud-specific cautions
- Atlassian’s article about hiding a screen-level None choice is explicitly Data Center only. Its HTML or script customization is not a Jira Cloud restoration procedure: Atlassian’s Data Center article.
- The exact current Jira Cloud administration UI labels and click sequence are not established here. If you use Jira administration instead of the API, locate the affected custom field’s context and option controls, and verify the context before saving.
- Restoring an option does not require changing whether a field is required or setting a default. Treat those as separate configuration decisions.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
