Summary

Setting a custom fields configuration to required makes it a required field under Request Types which is good. But when you make the field optional again from field configuration that is not updated in the Request Types field and is still required in the portal.
 

Environment

Steps to Reproduce

1. Create custom field, add to JSD project screens
2. Make custom field required from Field Configurations
3. Note that custom field is required under Request Types fields
4. Make custom field optional from field configuration
5. The custom field is still required under Request Type fields

Expected Results

• If making a field configuration as required updates the Request Types field to required, setting it to optional should also update the Request Type field to not required.

Actual Results 

• The field is left as required under the Request Type fields. So the user must make two changes to make the field optional. Once from field configurations and once from Request Type fields.

  Notes

Workaround

• User must manually update the request type fields after making a required custom field optional again from its field configuration