This form contains a hidden field that does not have a valid default value configured.

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

Summary

When raising a new request via the customer portal in Jira Service Management (JSM) Cloud, you may encounter the following error:

This form contains a hidden field that does not have a valid default value configured.

This issue can block customers from submitting requests and arises due to misconfigured hidden fields in the request form as below -

(Auto-migrated image: description temporarily unavailable)

Environment

Jira Service Management Cloud

Cause

This error typically occurs under the following conditions:

  1. A hidden field is required but lacks a default value.

  2. The field context or options for a custom field have been modified without updating associated request types.

  3. The default value set for the hidden field is invalid for the issue type linked to the request type.

  4. Changes made to field configurations are not adequately tracked, leading to misconfigurations.

Solution

To address this issue, follow the steps below:

Step 1: Identify the Problematic Field

  1. Navigate to Project Settings -> Request Management -> Request Type.

  2. Open the Request Type where the error occurs.

  3. Check the Fields section for any hidden fields that are required but lack default values.

Step 2: Configure a Valid Default Value

  1. Edit the configuration of the identified hidden field.

  2. Set a default value that aligns with the issue type's context and field configuration.

    (Auto-migrated image: description temporarily unavailable)

Step 3: Test the Request Form

  1. Return to Request types and preview the form in the customer portal.

  2. Submit a test request to confirm the issue is resolved.

If you cannot identify the problematic field or if the issue persists after implementing these steps, you can reach out to Atlassian Support for further assistance.

Future Enhancements

Atlassian is working on improving audit log coverage to include custom field context changes. This feature is still in the "gathering interest" phase, but you can track updates via JRACLOUD-74945.

Further reading -

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.