You are not logged in.

Announcement

 Téléchargez la dernière version stable de GLPI      -     Et vous, que pouvez vous faire pour le projet GLPI ? :  Contribuer
 Download last stable version of GLPI                      -     What can you do for GLPI ? :  Contribute

#1 2017-08-17 08:30:38

plcadmin
Member
From: Armidale, Australia
Registered: 2014-06-12
Posts: 13
Website

Auto solve tickets on no response

This has probably been asked before, but my searches just missed it smile

I want to be able to set up a rule or an automatic action that will look at a ticket, check if the technician was the last to update it, and check the time waiting for a response from the requester. If it is more that a preset time, then the ticket should be flagged as solved. This will generate the email to the user that solving a ticket normally does.

I know other ticketing systems, such as Web Helpdesk and Zendesk, can do this. I am just stumped on how I get there with GLPI.

Any suggestions greatly appreciated.

Ross

Offline

#2 2017-08-17 19:11:45

Roshan
Member
Registered: 2017-07-26
Posts: 69

Re: Auto solve tickets on no response

You can do it by auto close ticket after x days option under entity.
if u set 1 day, the ticket will auto close after 1 day after the technician has solved it.
Entity - Root Entity - Assistance - close tickets after x days.

Offline

#3 2017-08-18 01:40:00

plcadmin
Member
From: Armidale, Australia
Registered: 2014-06-12
Posts: 13
Website

Re: Auto solve tickets on no response

Roshan, thanks for getting back to me.

I have that in place, not really what I want.

I am looking at the scenario, for example, where the tech asks the customer for an update. 3 days later the customer still has not responded. I want the system to look at the time since the last update by the tech and set the status to Solved. I would take it that the Status would need to be changed from Processing(Assigned) to Pending to flag this type of action.This would then generate the autoclose on the ticket.

I thought I might be able to do it with a business rule, but the time and status do not appear to be available triggers for business rules.

Offline

#4 2017-08-18 10:39:34

grajek
Member
Registered: 2015-03-16
Posts: 72

Re: Auto solve tickets on no response

It's not possible out of the box. You need to make some developement on this. The easiest way would be writing some sql statement and run it on scheduler periodically.


GLPI 9.5.1 CentOS

Offline

#5 2017-08-18 11:19:03

yllen
GLPI-DEV
From: Sillery (51)
Registered: 2008-01-14
Posts: 15,278

Re: Auto solve tickets on no response

When a technician give a solution, the requester can approve this solution. So the ticket in Solved status becomes Closed status.
If the requester doesn't reply to approve or refuse the solution, automatic close in your entity's configuration can close your ticket.


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

#6 2017-08-20 23:58:50

plcadmin
Member
From: Armidale, Australia
Registered: 2014-06-12
Posts: 13
Website

Re: Auto solve tickets on no response

grajek, I agree. Might have to do some reading on the automatic action service.

yllen, the tech has not solved the ticket. They have, for example, asked for an update on the situation or asked the customer to take a specific action and send back the the results.

Offline

#7 2017-08-21 08:42:58

LaDenrée
HELPER
Registered: 2012-11-19
Posts: 6,167

Re: Auto solve tickets on no response

it looks like this planned feature :

http://glpi.userecho.com/topics/213-pen … ime-limit/


Trouver la panne avant de réparer...
GLPI10.0.10 (ubuntu 22.04 PHP8.1  Mariadb10.6 ) plugins : comportements 2.7.2 reports 1.16.0 formcreator 2.13.8, datainjection 2.13.4 fields 1.21.6

Offline

#8 2017-08-24 16:59:50

yllen
GLPI-DEV
From: Sillery (51)
Registered: 2008-01-14
Posts: 15,278

Re: Auto solve tickets on no response

You can perhaps define it in an SLA level actioned on max time to waiting status


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

Board footer

Powered by FluxBB