"Always Required" setting on the "User Custom Field" passes when set to the system default of "Unassigned".
I have already reached out to support for this and they are telling me that this is the way that it was designed. However, this makes very little sense if it was truly designed this way for the simply fact that having the ability to set a field to "Always Required" should force user interaction but since the system will accept the default of "Unassigned" it defeats the purpose of being a required field.
13
votes
