Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Karen Marques
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 8, 2021

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

2 answers

2 votes
Mikael Sandberg
Community Champion
February 8, 2021

Hi @Karen Marques,

Welcome to Atlassian Community!

If you hide a field on a service request you have to give it a default value. So go to your project settings > request type and select the form you have the hidden field on and then unhide the field, hide it and enter a value. 

Aaron Geister
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 11, 2021

I have this issue right now with a team managed project but there are no hidden fields. I have never seen this issue before in team managed project. Could this be a deleted field or maybe a approval field?

Atlassian B2X June 25, 2021

I am also facing same issue Request type side showing "This Request Type has no hidden fields." while raising issue time showing "This form contains a hidden field that does not have a valid default value configured"

Mike Low November 23, 2021

I'm getting the same issue. In order to try resolve it I made the hidden field unhidden so displays to user. Also made it optional with no value but still get the error. Not sure what else the system could be seeing as a hidden field when there are none showing  2021-11-23_11-58-48.png2021-11-23_12-01-01.png

Mike Low November 23, 2021

Found the fix here - https://community.atlassian.com/t5/Jira-Service-Management/all-project-suddenly-getting-hidden-field-error/qaq-p/978411.

The error message pointing out that it relates to the hidden field is misleading in that it is not the hidden field configured on the SM screen above but one of the many other hidden fields configured outside of SM - see the 8 of 29 referenced in screenshot above). If you go and create the issue via Jira Server (not Service Management) the error will be more descript. In my case I had a custom field for CAB approver with a default value of a user that had previously been deactivated. Removing that user from the default list solved the issue.

0 votes
Fustina Orazu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 17, 2023

Go to the Project settings of the Service project

then click on "Details", check if the Project lead is someone who has been deactivated and change it to someone who is active

then go to "Internal access" and also check if it is updated.

Casey Richmond
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 7, 2025

This worked for our organization.  Project Lead left, I updated the name to the new Project Lead, and the customer was able to submit the ticket.  This is in JSM

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events