In Jira Cloud, a missing “None” or default value can mean several different things: a new work item is not receiving its configured default, an older item is still blank, or an empty field is hidden from the view. For new work items, check the custom field’s context and default value, then confirm that the context covers the project and issue type you are creating. A default does not fill in older records, and a Data Center workaround for displaying empty fields is not a supported Cloud fix.
First identify what has disappeared
“None” may describe an empty field, a literal option named “None,” or a missing default. The right fix depends on when and where the symptom appears:
As an Amazon Associate I earn from qualifying purchases.
- On the create form: the field may have no applicable default, or its context may not cover the project or issue type.
- After creation: an existing work item that was blank will not be populated merely because you changed the default.
- During creation: an invalid or missing custom-field default or context can cause a creation error, including when the field is not visible on the form.
- On the work-item view: an empty field may simply not be displayed. That is different from setting a stored value.
The available documentation establishes these possible causes, but the symptom alone does not identify which field, form, project, or issue type is responsible in your Jira site.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair the default for new work items
For Jira Cloud, start with the custom field’s context and default configuration. Atlassian says that invalid or missing custom-field defaults or contexts typically underlie the creation errors covered in its Jira Cloud troubleshooting guidance.
#1 Best Overall
- Open Jira settings, then go to Work items (or Issues, depending on the administration navigation) and choose Custom fields.
- Find the affected field and open Contexts and default value.
- Review the default and confirm that its context applies to the project and issue type where creation failed. Check for an additional context that is incomplete or misconfigured.
- If an error identifies a custom field by ID, map that ID to the field in administration before changing anything.
- Retry creating a work item using the same project and issue type that produced the problem.
Atlassian’s Cloud administration guide to field contexts describes contexts as the place to configure defaults for open text fields and options for fields with choices. Its text-field example says the default populates the text box when a work item is created.
Confirm the context covers the right issue type
A default can be valid but still not apply to the work item you are creating. Contexts can scope a field to projects and issue types, and defaults can vary by issue type within a context. The Jira Cloud REST API reference for issue custom-field contexts distinguishes a catch-all default from one tied to a particular issue type:
Rank #2
- Used Book in Good Condition
- An entry with
isAnyIssueType: trueis the catch-all for issue types in that context that do not have a more specific entry. - An entry with a specific
issueTypeIdapplies only to that issue type.
So a default that appears for one kind of work item may be absent for another, or may differ after you switch projects. Verify the actual field-to-context mapping and applicable issue type before editing the default.
Know what changing the default will—and will not—change
A field default is a creation-time value; changing it does not retroactively populate existing work items that were already blank. Atlassian Community discussion on custom-field defaults and the view screen makes this distinction. If historical records need values, treat that as a separate data-update task: choose a method appropriate to the field type and check workflow and reporting consequences before applying changes in bulk. There is no single bulk-update procedure established for every field and site.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Do not use the Data Center “visible None” workaround in Cloud
Atlassian’s article about making an unselected select-list field visible as “None” or “Not Available” is explicitly marked Data Center Only. It discusses replacing the built-in empty state with a literal option and warns that the guidance may not apply to current Jira versions. It is not a Jira Cloud recovery procedure: do not carry its Velocity-template or HTML/JavaScript customization into Cloud.
These are different outcomes, not interchangeable fixes:
Quick Recap
| What you want | Where to look | What the evidence supports |
|---|---|---|
| New work items should receive a value | Cloud custom-field context and default; check project and issue-type scope | Cloud field configuration and creation behavior are documented by Atlassian. |
| An existing blank work item should gain a value | A separate update to the existing data | Changing the default alone does not backfill older records. |
| A blank field should show a visible placeholder on the item view | Do not apply the cited Data Center instructions to Cloud | The available “visible None” instructions are Data Center-only; they do not establish a supported Cloud equivalent. |
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
