You are not logged in.
Pages: 1
Hi Guys
Now we've upgrded to 0.78.1 I've noticed that when our service desk enter a ticket for a member of staff, once we enter a solution and change the status to solved, it then shows on their screen as waiting to be closed.
Can you explain how I can set them to close automatically when we solve it, or how the automatic actions can work to do it.
At the moment it seems to mean we have double the work to do to close a ticket.
Offline
Look under "Automatic Actions" for closeticket schedule. I believe it's what is causing it to close tickets. Try disabling it and see if it fixes the problem.
Offline
Hiya,
I'm now trying to figure our the same thing... we set the tickets to Solved via the Solution tab.
Is the design that the autoclose now comes along and puts the ticket state to "closed". If so, whats its selection criteria, is it time based ??
I think imunro01's original question isn't that the closing is a problem, its that it *wasn't* closing it automatically, and/or that it wasn't being set to closed as part of the resolution. Which is the same issue I've hit after the upgrade.
GLPI 0.83.91/CENTOS5 - OCS 1.01/Win2003
Offline
Can you explain how I can set them to close automatically when we solve it, or how the automatic actions can work to do it.
- In your entity's configuration, you choose Automatic closing of the tickets after : Value of global configuration
- and in your global configuration (Setup > Genaral > Assistance tab) Automatic closing of the tickets after : 0 days
Like this, when a ticket is solved, i's immediatly 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
Hi Yllen,
Yes thats how my GLPI is configured, both in Root Entity and Assistance Tab...
So should tickets be closing immediately when we submit the Resolution, or, when the closeticket script runs ?
At the moment, tickets go to a Solved state, but I've not noticed if they're going to "close".
I'll try it out with a test ticket.
GLPI 0.83.91/CENTOS5 - OCS 1.01/Win2003
Offline
Ah actually... answered my own question... it closed a ticket automatically this morning...
Am I right in thinking that the reason behind having a separation of Solved and Closed is to give end-users a chance to respond to the solution if they want to ?
GLPI 0.83.91/CENTOS5 - OCS 1.01/Win2003
Offline
Don't put autoclose ticket to 0 day but to 1 day (end-user will have 1 day to respond to the solution)
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
Pages: 1