You are not logged in.
Pages: 1
Hello,
I've problem with solutions tickets and SLA. For example: Requester refused solution, but cron_slaticket automatic close ticket when change SLA.
181218 2011-08-31 16:04 cron_slaticket Resolution date "" --> "2011-08-31 16:04"
181217 2011-08-31 16:04 cron_slaticket Status "W toku (przypisane)" --> "Rozwiązane"
181216 2011-08-31 16:04 cron_slaticket Escalation level "Manager" --> " "
181215 2011-08-31 16:04 cron_slaticket Solution - Description modification of field
181214 2011-08-31 16:04 cron_slaticket Description modification of field
181185 2011-08-31 15:51 User Follow-up add an element :Follow-up (5540)
181184 2011-08-31 15:51 User Resolution date "2011-08-28 14:22" --> ""
181183 2011-08-31 15:51 User Status "Rozwiązane" --> "W toku (przypisane)"
If I don’t use SLA problem not exist.
GLPI 0.80.2
Debian
Thanks for your help. Regards!
Lukasz
Debian 5.0 Lanny / GLPI 0.80.2 / OCS 2.0
400 Computers / 250 users
Offline
Maybe you set "Automatic closing of solved tickets after :" value under
Setup -> General -> Assistance
too low?
Offline
I don't use this option.
I've set "Automatic closing of solved tickets after : Never"
Debian 5.0 Lanny / GLPI 0.80.2 / OCS 2.0
400 Computers / 250 users
Offline
Any ideas?? BUG??
Debian 5.0 Lanny / GLPI 0.80.2 / OCS 2.0
400 Computers / 250 users
Offline
I don't really understand your problem and i can't read "Status "W toku (przypisane)" --> "Rozwiązane" ??
JMD / Jean-Mathieu Doléans - Glpi-project.org - Association Indepnet
Apportez votre pierre au projet GLPI : Soutenir
Offline
What are rules of your SLA ?
By example, If you write in SLA for a level Status assigned Closed even the solution is rejected, the ticket will be closed
CentOS 6.5 - CentOS 7.x
PHP 5.6 - PHP 7.x - MySQL 5.6 - MariaDB 10.2 + APC + oOPcache
GLPI from 0.72 to dev version
Certifiée ITIL (ITV2F, ITILF, ITILOSA)
Offline
I don't really understand your problem and i can't read "Status "W toku (przypisane)" --> "Rozwiązane" ??
"Status "W toku (przypisane)" --> "Rozwiązane" is "Status "Processing (assigned)" --> "Solved"
What are rules of your SLA ?
By example, If you write in SLA for a level Status assigned Closed even the solution is rejected, the ticket will be closed
Priority Assign Very High
Automatic reminders of SLAs Send Yes
This problem don't exist always if I find resolved I will write.
Debian 5.0 Lanny / GLPI 0.80.2 / OCS 2.0
400 Computers / 250 users
Offline
Pages: 1