nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

rangel de oliveira machado

Good afternoon,

I created a project in Jira Service Desk, made the priorities settings x SLA and costumisei the services catalog. When I register a request the following message appears

Already exclude the Priority field and include again I changed the priority but did not resolve this issue.

Can someone help me?

Accepted answers

All comments

Nic Brough -Adaptavist-

A service desk request is a layer that goes on top of a JIRA issue. The JIRA issues are usually more complex and detailed than the requests and have a lot more fields, with only a few shown to the customer making the requests.

If you have configured the JIRA issue to have a mandatory field that must be filled in, then either the Service Desk Request must ask the customer for it, OR you can set a default value for it and the issue will assume that is the value when a customer creates an request/issue.

You have at least one field that is mandatory in the issue, but not mapped or defaulted.

To find and fix this:

Log in as an agent in that Service Desk and click "create" from the JIRA header.
This will take you to a screen that to create the plain JIRA issue.
Mandatory fields will be marked with a * to show you need to fill them in.
Take a note of all of them, and check if they are defaulted.
Try creating the issue and check that you don't get any "field is mandatory but not on screen" errors
If you do get errors here, it should tell you what fields you need to add to the screen - do that and try a new request

Finally, go over the list you made. For every mandatory field, you must do one of these three:

Make it optional in JIRA
Make sure it is on the Service Desk Request form
Set a default value for it in JIRA's settings for the field

Barion Operators

Hi,

I have the same issue.

I run through the steps you suggested and I was able to create the ticket without any problem. The only mandatory field was the summary (beside the issue type, and project)

So I stuck now. What else can I check?

ps.: I have a Request type hidden from the portal. Can it cause the issue?

Thanks.

Olha Melnychuk

Hi,

I also have the same issue. Steps above are not helping.

futurewei001

I meet similar problem and find a way out, my problem is that I have a customized field have default value conflict with field filtering.

The field is a single user picker, hope can help...

Shankar Narayanan_s6iq99

Thanks!

In a custom field, we have set a default value and also a filtering.

We cleared both and the particular issue resolved.

Yongwon BAEK_3z4dfk

sorry

Jhonattan Lima Campos

thank you for explining, my problem is resolved.

Ashly Montaño

Hello,
I am experiencing the same issue with the error message: "Error This form contains a hidden field that does not have a valid default value configured." However, this problem is occurring in a team-managed project in Jira Cloud. This means that when I try to create an Issue Type in Jira, the form detects a mandatory field that is not visible to the user and does not have a correctly configured default value.

I have attempted to resolve the problem by creating another Issue Type that only contains the "Summary" field, but the error still appears. I need guidance on how to resolve this situation to ensure that all mandatory fields are properly mapped or assigned an appropriate default value.

Glenn Castillo

Solution (for us)

We had this issue today. It turned out that some forms under Project Settings > Request Types were not saved properly (?). I am not sure how this happens, but I noticed that the "Save changes" button was lit blue, which is otherwise greyed out when the form is saved.

I just pressed the "Save changes" button, and the form in the customer portal worked again without any error.

Sébastien Nicolas_9w9m6o

Hello,

I also encountered this issue after migrating from version 9.12 to 10.3.

None of the solutions above worked for me — there were no hidden fields in my configuration or forms.

In the end, I resolved the problem through the Assets - Roles configuration.

In my project, I had an object schema linked that didn’t have the proper permissions for Jira Service Management customers.

Once I enabled this permission, it suddenly worked!

I took me time to find out.. Hope it will help other :-)

s_gridnevskii

Not sure if this is still relevant in 2026, but I just solved this mystery and it may help others.

So the error is misleading in a way that the phrase is not correct. It should be something like

"Jira could not create the issue since the value of one of the fields is missing or incorrect".

How to fix.

1. Check fields on the new issue screen. You can do that by clicking Create and selecting issue type in agent's view.

2. Find fields that are with red dot. Check that they are whether on request form or have predefined value in form constructor.

3. Find fields that have default values, e.g. user or date fields.

4. Make sure these default values are valid

it can happen that a date format is incorrect, or user that is in the field by default left company.

How to diagnoze.

For data center it is easy. Just go to /var/atlassian/product/log/atlassian-product.log and check last error. It will give you field name.

For cloud I guess it is worth trying creating an issue with REST API and see what server returns along with an error, maybe field name will be there.

Resume

1. Check obligatory fields
2. Check fields with default values