Is this a bug or I do not know how to use it ?
Hello Otrs Team, I am using OTRS 1.3.2 The Unlock time out (minutes): is 480 in the attachment you can see the picture for one in trouble ticket. The follow up was received at: 19:06 so it is normal that It should be unlocked after 480 minute (aprox 01:06 next day). Unfortunately the unlock was done at 19:35. Looking into my cron jobs I can see: 35 * * * * $HOME/bin/UnlockTickets.pl --timeout >> /dev/null That means the UnlockTickets is going to unlock all the tickets every hour no matter if the ticket unlock time out is OK or not. Any ideas ? Daniel -- This message was scanned for spam and viruses by BitDefender For more information please visit http://www.bitdefender.com/
Hi Daniel, Daniel Balan wrote:
I am using OTRS 1.3.2 The Unlock time out (minutes): is 480 in the attachment you can see the picture for one in trouble ticket.
The follow up was received at: 19:06 so it is normal that It should be unlocked after 480 minute (aprox 01:06 next day). Unfortunately the unlock was done at 19:35. Looking into my cron jobs I can see: 35 * * * * $HOME/bin/UnlockTickets.pl --timeout >> /dev/null That means the UnlockTickets is going to unlock all the tickets every hour no matter if the ticket unlock time out is OK or not.
Any ideas ?
%s is a minor bug in Language.pm module (Get function) that exposes itself when ticket_history table record lacks some fields. Nothing serious. A patch such as this one would help: --- otrs-1.3.2-01/Kernel/Language.pm 2004-06-15 11:16:34.000000000 +0200 +++ otrs/Kernel/Language.pm 2004-12-08 13:19:27.000000000 +0100 @@ -217,6 +217,8 @@ } } } + # clean out remaining %s'es - added by ddzeko + $Text =~ s/\s*\%\w//g; return $Text; } else { (Just need to add this one line ($Text =~ s/...//g) in line 217.) Ticket unlocking problem has already been answered. Look into mailing list archives. http://www.mail-archive.com/otrs%40otrs.org/msg06256.html Regards, Damir
participants (2)
-
Damir Dzeko -
Daniel Balan