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
"Error This form contains a hidden field that does not have a valid default value configured"
Already exclude the Priority field and include again I changed the priority but did not resolve this issue.
Can someone help me?
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.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks!
In a custom field, we have set a default value and also a filtering.
We cleared both and the particular issue resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I also have the same issue. Steps above are not helping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
Finally, go over the list you made. For every mandatory field, you must do one of these three:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you for explining, my problem is resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Ashly Montaño 👋 This is a very old thread dating back to 2017. While it's great that you search the community for an answer before posting a new question, this is a case where a new question is appropriate (assuming you followed the advice from @Nic Brough -Adaptavist- ), and that did not help.
Best,
-dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.