Hidden fields do not have preset value error

[Warren Zingel]

I have a number of configuration errors on a Jira Service Management project which states:

---

The {Request Type/Form name} request form contains configuration errors

The following hidden fields on the request type do not have the required preset values:

• Impact
• Urgency

To repair this request type, set a value for these fields at the fields page.

---

However when I look at the request type or forms, these fields are not available under the suggested fields list.  Where can I look to tidy up these errors?

[Kris Dewachter · Accepted solution]

Hi @Warren Zingel ,

If the fields are not listed under the suggested fields, they are probably already included in your request type form (as the error message suggests).

Can you check if your "Request Form" of the "Request Type" contains those fields and are marked as "hidden" ?

Best regards,

kris

[Warren Zingel]

Hi @Kris Dewachter , thanks for your response.  Unfortunately this was one of the first things I checked and it doesn't seem to be that simple.  It more as if the fields have been deleted, but still referenced in some way.

As you can see the request form is very simple (and I've checked under the issue view tab too) but the fields relating to the warnings are not on the form, not under the fields list.  I think I need to do something more fundamental to repair the fields, but I'm not sure how.

[Kris Dewachter]

Hi @Warren Zingel ,

Did you check if the custom fields actually still exist and still assigned to the project and screens ?

[Warren Zingel]

That's where I could use some guidance thanks @Kris Dewachter 

[Kris Dewachter]

@Warren Zingel ,

Firstly, you can check if the fields actually exist by going in Jira to "Settings" --> "issues" --> "Custom fields"

Try searching for your fields in the "Active" and "Trash" tabs.

If they don't exist or are in the trash, that is probably the cause of the issue.

If they exist, check the "Screens and Contexts" and "Projects" settings.

Also, in the project and issue type where the fields are supposed to exist ... open an issue. In the top right corner, click on the "3-dot icon" and click on "Find your field" to check why the field is not being displayed.

[Warren Zingel]

Thanks @Kris Dewachter that's put me on the right track!  Looks like the fields that are causing the error have no contexts set, however given the fact these fields are not currently used, I suspect it will be neater for me to move them to trash.

I've tested trashing one of the fields on Sandbox (Impact) and have verified that has removed it from the configuration errors being reported, so I'll recommend this course of action with the change team.

Thank you for your help in this matter.