Mandatory fields added to tickets are not respected

[verdanatech-marcio]

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

10.0.17

Plugin version

1.21.17/1.21.18

Bug description

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

10.0.17

Plugin version

1.21.17/1.21.18

Bug description

An additional field has been added to the call form. When opening a call, it is required, but when solving a call, it is empty. The call is solved without the need for the field.

Relevant log output

No response

Page URL

http://localhost/glpi/ticket.form.php

Steps To reproduce

No response

Your GLPI setup information

No response

Anything else?

No response

[stonebuzz]

The form for adding a solution is not linked to the ticket form. As a result, the status constraint does not apply here. In fact, these two forms are distinct, each having its own container and its own constraints (because depending of differetns GLPI object (Ticket / ITILSOlution).

If the aim is to make this field mandatory when resolving a ticket via the ‘Add a solution’ button, we would need to add this field to the ‘ITIL Solution’ object and make it mandatory at this level. Unfortunately, as things stand, this is a technical constraint that cannot be easily circumvented.****