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

Field is required even though not on screen

Shamsudeen Shaikh

I have a custom field (required) configured on a specific screen, However when I try to create a new issue JIRA complains of field being required.

My create screen and screen which has the custom field are different, Also I verified in field configuration "screens" option.

I think the field is getting tied up somewhere, but cant figure it out.

Regards,

Shamsudeen

Accepted answers

All comments

Fabio Racobaldo _Catworkx_

Hello,

a custom field that has been defined as required into Field Configuration scheme is required into the creation screen even if it is not present there.

If you need to define a custom field required for a specifc workflow transition (different from creation), you could install JIRA Suite Utilities plugin and add a Validator (Fields Required) for your transition.

Hope this helps,

Fabio

Fabio Racobaldo _Catworkx_

Please, mark this field as option into your Field Configuration Shceme and take a look here for more information about Fields Required validator configuration https://jsutil.atlassian.net/wiki/display/JSUTIL/JIRA+Suite+Utilities+Workflow+Validators

Regards,

Fabio

Shamsudeen Shaikh

Thanks a lot ... That works...

Fabio Racobaldo _Catworkx_

You're welcome. Please mark my answer as accepted.

Regards,

Fabio

Basavaraj Nesargi

But the required field will not have an asterisk(*) mark by using the Fields Required validator.