
I seem to be missing something here. I have set the unlock timeout on my queue / sub queues, but nothing I seem to do makes the ticket unlock. Escalation is working perfectly. Is there some point that I am missing. OTRS Version 2.1.5 SuSE 10.1 Ticket status any Many thanks for your help. --Shawn

Hi Shawn, Shawn Beasley schrieb:
I seem to be missing something here. I have set the unlock timeout on my queue / sub queues, but nothing I seem to do makes the ticket unlock.
Escalation is working perfectly.
Is there some point that I am missing.
OTRS Version 2.1.5 SuSE 10.1
Ticket status any
var/cron/Unlock must be run (by cron) for executing the automatic unlocking mechanismn.
Many thanks for your help.
--Shawn
Bye, Alex

Alexander Scholler schrieb:
Hi Shawn,
Shawn Beasley schrieb:
I seem to be missing something here. I have set the unlock timeout on my queue / sub queues, but nothing I seem to do makes the ticket unlock.
Escalation is working perfectly.
Is there some point that I am missing.
OTRS Version 2.1.5 SuSE 10.1
Ticket status any
var/cron/Unlock must be run (by cron) for executing the automatic unlocking mechanismn.
Many thanks for your help.
--Shawn
Bye, Alex _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
I have found it as well. Thanks. But what I do not understand it the best logic to use when planning the cron job. My unlock times are: 1 10 20 1440 2880 The standard settiing is 35 mins. The best time I can think of see is every 2 minutes. Any ideas? --Shawn
participants (2)
-
Alexander Scholler
-
Shawn Beasley