Mandatory Yes/No field does not respect default value "No" in ticket form

[OteJlo]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

GLPI Version

11.0.2

Plugin version

1.23.0

Bug description

When adding a Yes/No field as mandatory in a ticket form, the default value is set to No. However, if the user leaves the field as No, the form validation fails, and the ticket cannot be submitted. The mandatory check only works when the value is changed to Yes.
This means the mandatory field logic does not work correctly for Yes/No fields, as the default value "No" should be considered valid when the field is required.

Steps To reproduce

1. Go to Fields plugin configuration.
2. Add a new field of type Yes/No.
3. Set the field as mandatory.
4. Assign it to a ticket form.
5. Create a new ticket and leave the field as No (default value).
6. Try to submit the ticket.

[stonebuzz]

Hi @OteJlo

maybe this -> #1083

should solved your issue.

Best regards

[OteJlo]

Hi @stonebuzz ,

I just updated the plugins to version 1.23.1, but the problem is still there.

The GLPI version is still 11.0.2.

Thanks in advance, have a great day.

[stonebuzz]

I’m unable to reproduce the issue on my side. Could you please provide the container configuration, the field settings, and any other relevant information here?

[OteJlo]

Yes, I can take some screenshots for you

fields_conf.yaml

When I set ENVPNFIELD as mandatory, and also set it as mandatory in the ticket form, with the default setting at “No,” it indicates that it has not been selected.

It is important to click “Save” again on the form so that it recognizes that the question is mandatory.

And then, when you try to create a ticket leaving the choice set to “No,” you get an error, but then you just need to make sure it's not set to mandatory and it works.

[stonebuzz]

@ccailly can you take a look ?