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

Getting Field Required even though field is not part of screen

Jon Starbird

I have a Custom Field that was part of the main default screen and I have since removed it however when we create an issue it is still saying the field is required.

I've gone through all the places I could think of to find where it might be but it is not listed for this screen anywhere.

Where in the database could I look and possiblly update it to properly remove the field?

Thanks,

Accepted answers

Natalie Hobson

You need to check the field configuration you are using with your field configuration scheme:

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour

Although the screen dictates whether or not the field is there, the field configuration can dictate whether or not it is hidden, required, ect.

All comments

Natalie Hobson

You need to check the field configuration you are using with your field configuration scheme:

https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour

Although the screen dictates whether or not the field is there, the field configuration can dictate whether or not it is hidden, required, ect.

Natalie Hobson

Whatever issue types you have associated with that field configuration will require that field if you have set it to be required - regardless of whether or not you actually have it on the screen.

Jon Starbird

It is required there as I have it on another Screen which it does show that screen and only that screen listed for it.

Jon Starbird

Ok. Doesn't make sense but I can work around that. Would seem it would only be required on the Screen that it is part of.

Thanks,

Welcome!

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

Quick Links

Find more posts tagged with

jira