How to Fix Invalid Custom Field Default Value Errors in Jira Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
Users are unable to create new Jira work items and are getting similar error messages:
Error 1: Couldn't send the request. This form contains a hidden field that does not have a valid default value configured
Error 2: Change Managers. Pick another user, as the selected user doesn't exist
Error 3: Couldn't create the work item. We're having some trouble creating the work item. Refresh the page and try again.
All three error messages above are typically caused by the same underlying issue: a custom field in the field configuration has an invalid or missing default value or context. Follow the steps below to identify and correct that field. The field named in the console log may not be visible on the create/request form itself — it can still be part of the field configuration. This is common for a global-context custom field with an invalid default value, or a field migrated from server to cloud whose context was never configured.
Solution
Diagnosis steps:
Open browser DevTools console - reproduce the error with the console open (F12 → Console tab). Look for the API response that names the offending field ID or field name.
Fix or clear the invalid default value - navigate to the field's configuration and update or remove the default (e.g., pick a valid, active user or select a valid option).
Re-check hidden fields - in the space's field configuration scheme, review fields marked as Hidden. A hidden field with a stale default still blocks work item creation eventhough the user never sees it on the form.
Detailed walkthrough follows below.
Invalid values on custom fields
This error message is shown because an invalid value has been configured or selected for some other field that belongs to the field configuration. The field could either be pointed out in the error message or the field could not be specified as well. In this case, it would be necessary to check the browser console logs to identify the problematic field.
Useful information on how to access console logs:
Also, it is important to note the following:
The field specified is sometimes not even added to the request form, but is usually a part of the field configuration or
The field specified is a custom field that has a global context and is applicable to all issue types but has an invalid default value setup
If the field specified, is a field migrated from server to cloud, then sometimes, the context is not configured at all.
Checking the console logs would point out the field that has the error as seen below:
{"errors":[\{"errorMessage":"This form contains a hidden field that does not have a valid default value configured"}
{"errorMessage":"User 'Former user' is not valid for this user picker.","field":"customfield_10663"}],"reasonKey":"validation.error","reasonCode":"400"}OR
A validation failure occurred when a customer attempted to create a request with issue type 'Service Request'. The hidden field 'Change managers' is required and does not have a default value set.OR
{
"errors": [
{
"errorMessage": "This form contains a hidden field that does not have a valid default value configured"
}
},
{
"errorMessage": "Specify a valid value for '<customfieldname>'. The allowed values are , -1",
"field": "customfield_XXXXX"
}Edit the custom field context and default value
When the error message refers to a custom field ID, the following documentation can be used to find out which custom field is being specified.
Once the custom field has been identified, navigate to the custom field's configuration by following the steps listed below:
Select Cog Icon > Issues.
Under FIELDS, click Custom fields.
Search for the custom field identified earlier, click the 3 dots > Contexts and default value. Alternatively, you can click a field's screens or contexts link and then click Contexts > Create, edit or delete contexts.
Other possible values that could be seen for the Default Value include <User Name>, unknown.
The <user name> could refer to a previous user who was recently removed/deactivated from the site.
To edit or remove this default value, the following steps need to be followed:
From the screen above, select Edit Default Value.
Enter a valid value or remove the invalid value that is causing issues.
Save and exit.
Now, the errors seen earlier should not be displayed and the user should be able to create new issues.
If it is a configuration issue related to context, follow the steps below to resolve the context error:
Navigate to the custom field page of your site: https://<yoursitename>.atlassian.net/secure/admin/ViewCustomFields.jspa
Search for the field and click the three dots beside it.
Go to Context and default values.
Delete any additional context that might have been set for the field and which is incomplete.
After the corrective steps listed above have been taken, the request can be submitted from the portal again and ticket should get created without issues.
How do I know it worked?
Create an issue using the same project and issue type that previously failed. The create form should submit without the "hidden field / invalid default" error.
Related articles:
Was this helpful?