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; } } }

all project suddenly getting hidden field error

Ken Yuan

Hi Everyone,

This week, we suddenly start to get the

"Error

This form contains a hidden field that does not have a valid default value configured" when raise a request.

No change were made and we even tried to create a new project from scratch just to isolate the issue and still unable to fix this. Has any experience this?

Thanks,

Accepted answers

Maciej Egermeier

In my case there was a user picker field with default values. In custom field default values there was a user which is inactive. When you try to create this ticket from "backend" it will show proper error. But from the portal you will see this meaningless error.

All comments

laralg

Hello Ken,

Maybe in one of your service desk forms you have a field that is hidden which had a default value that has been deleted.

This happened to me.

ej. Having a component hidden, with a value, and someone deleted the component that I set up.
Check the hidden fields of your request form to see if all of the default values are correct.

Regards

Ken Yuan

Hi Lara,

Thank you for your reply and help, is there any good way of finding the hidden field?

I have cross checked both field configuration and request type fields and none of field were hidden apart from assignee and Summary.

Thanks,
Ken

laralg

Hi Ken,

The problem might be that there was a hidden field and you deleted the customfield. And sometimes you need to be carefull and delete fields in request before customfields. Check de audit log for deleted customfields, and see if there is something. You might have to create a customfield with the same name to link and unlink again, from the request form.

Regards

Maciej Egermeier

David Lunsford_eo9fj2

I had the same issue. One of the Global Jira Administrators added a Multi-select user picker without a default value (user) set. The field wasn't needed as I am a strong believer in leveraging Jira Project Roles for workflow approvals ... delete the field and use Jira Project Roles.

sandipta sucharita_gyqxlr

Helped me to solve the issue. Thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk