Mario,
We acknowledge that this issue occurs on our recent builds of
ServiceDesk Plus. Here's the referenceID to track the availability
of the fix, SD-34932
Jai Anand K
ServiceDesk Plus