You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever user is trying to create ticket with selected SLA plan/time , error is producted. (Only in debug mode you can see error code)
Error showed in debug mode:
Uncaught Exception TypeError: Unsupported operand types: int + string in /var/www/html/glpi/src/LevelAgreement.php at line 855
Relevant log output
glpiphplog.CRITICAL: *** Uncaught Exception TypeError: Unsupported operand types: int + string in /var/www/html/glpi/src/LevelAgreement.php at line 855
│ Backtrace :
│ src/Ticket.php:449 LevelAgreement->computeDate()
│ src/Ticket.php:1428 Ticket->getDatasToAddSLA()
│ src/Ticket.php:2027 Ticket->slaAffect()
│ src/CommonDBTM.php:1297 Ticket->prepareInputForAdd()
│ front/ticket.form.php:80 CommonDBTM->add()
│ public/index.php:82 require()
Page URL
No response
Steps To reproduce
Ticket template: Time to resolve- required
Create ticket with SLA/OLA plan selected.
Your GLPI setup information
yesturday upgraded from 10.0.10 to 10.0.12
Anything else?
This is pretty important bug, as support can't create tickets as expected.
Workaround- Turn off mandatory field TTR.
When TTR is empty, ticket is created as expected.
The text was updated successfully, but these errors were encountered:
Code of Conduct
Is there an existing issue for this?
Version
10.0.12
Bug description
Whenever user is trying to create ticket with selected SLA plan/time , error is producted. (Only in debug mode you can see error code)
Error showed in debug mode:
Uncaught Exception TypeError: Unsupported operand types: int + string in /var/www/html/glpi/src/LevelAgreement.php at line 855
Relevant log output
Page URL
No response
Steps To reproduce
Ticket template: Time to resolve- required
Create ticket with SLA/OLA plan selected.
Your GLPI setup information
yesturday upgraded from 10.0.10 to 10.0.12
Anything else?
This is pretty important bug, as support can't create tickets as expected.
Workaround- Turn off mandatory field TTR.
When TTR is empty, ticket is created as expected.
The text was updated successfully, but these errors were encountered: