Answer
This has been reported as a known display defect (custom fields visually appearing mandatory when they aren't) rather than an installation-specific problem — if you see this exact symptom, it's worth checking whether your release already includes the fix rather than troubleshooting your own environment's setup, since it's been confirmed to R&D as a genuine bug rather than expected behavior.