I agree. I brought this up before and was told I was wrong

See #24982

Totally agree, if you can choose 2 options (Yes/No) then it's not required as you do not have the option to not choose anything.

Asterisk should be removed.

Totally agree, if you can choose 2 options (Yes/No) then it's not required as you do not have the option to not choose anything.

#24982 (comment) and follow on comments still stand. Just because you don't have a way of submitting a non-empty value through the UI does not mean that the form field definition should not have a required attribute if the application data model states that the field cannot be stored with a non-empty value, especially now that Joomla claims to have an API (and this API for some strange reason elects to use form definitions in a number of locations). Sadly, the only way to enforce the "this field cannot be stored with an empty value" server-side validation rule because Joomla does not have a proper validator API (a proper validator API is something like those in Symfony or Laravel where data models can be validated at will regardless of input source, not the Joomla\CMS\Form\FormRule class) is with the use of the required attribute, which bleeds into the frontend display. But hey, too late to do anything for 4.0 on that topic now.

This should be closed for the reasons stated above

@Quy What extra information are you asking for /me confused

Sorry I don't remember. Close?