Required field affecting all request types

Question

I made a field required in the Field Configuration and then afterwards went back and made it Optional again.  For some reason now though, all the request types have this field in there as Required even though 1- they didn't have the field in there before and 2- I have changed it back to Optional.  Why would this be?  Is this a bug or by design?

John Funk · Answer

Yeah, I guess that prevents the form from failing if the field is required and is not on the form.

rmax · Answer

Ok thank you, I thought they stayed in Suggested Fields and then had to be dragged over but maybe where it was already in some forms, when I made it Required, the system thought 'hey you field, you should be in all of the forms'

John Funk · Answer

Well, not sure what you tell you. If you make it required at the Field Configuration level, then that means ALL issues must have the fields populated when you create the issues. Therefore the fields must be on all forms that use that issue type.

But if you then make the field optional, the system has no way to know that you don't want the fields to be on the form at all. You can have fields on the form that are not required.