I've been getting these messages via email, is this something that I should be
concerned about or is there a way that I can disable these emails?
ERROR: No Ticket::StateAfterPending found for 'Pending Auto Close' in
Kernel/Config.pm!
Thanks!
-Jeff
___
Laurent Minost wrote:
OK Perl itself (as a language) is not the culpit but maybe the way
it is coded here can be improved ? Or maybe is it mod_perl ?
mod_perl in itself is not slow and certainly faster than running OTRS
as CGI.
I tried a few weeks ago to rewrite some simple parts of the c
Hi Nils,
It would be too much work to rewrite it to PHP.
But that's only an observation from myself, all tests I did to see where
was the problem
of this regular slow impression in OTRS leads me to the code, after
eliminating Web Server performance/tuning, DB backend ... OK Perl itself
(as a lan
Laurent Minost wrote:
DB backend were never the problem in all my cases and always though
that Perl is the culpit.
PHP/MySQL seems to me solutions easily faster than Perl one for Web
applications...
I really doubt that the language is the problem. Perl is a very
mature and fast language (
Hi,
You can use a Generic Agent and select Delete Ticket = Yes at the bottom
of your Generic Agent task to delete old tickets from your OTRS.
I don't really know if it will improve a lot your general OTRS speed, it
depends mainly on how SQL statements are builds in source code ...
I advise you to
pri pri wrote:
> hi all
>
> i have loads of e-mails in my system and my system has become really
> slow. i am running OTRS on windows server 2003. i would like to know how
> i can clear the database by deleting all the closed tickets. i want to
> know if this will help increase the system speed?
>
hi all
i have loads of e-mails in my system and my system has become really slow. i
am running OTRS on windows server 2003. i would like to know how i can clear
the database by deleting all the closed tickets. i want to know if this will
help increase the system speed?
thank you
___
Sorry,
I was first thinking you were talking about escalation :o/
For TicketAge, its name describe it well so I think the default OTRS
behaviour is the good one.
BR,
Laurent Minost
Le vendredi 31 août 2007 à 09:19 +0200, Laurent Minost a écrit :
> Hi Matas,
>
> I was thinking it was the defa
Hi Matas,
Matas Labasauskas schrieb:
Hello,
by default Ticket Age is increasing from creation moment.
Would by nice to know, is it possible to get Ticket Age increasing
only during set (9:00 - 18:00) working hours?
Ticket age if always increasing, even if the ticket was closed.
In contrast, t
Hi Matas,
I was thinking it was the default behaviour if you selected a Calendar
with specified hours on your queue settings ? Did you check on the doc
or try this please ?
Best regards,
Laurent Minost
Le vendredi 31 août 2007 à 10:04 +0300, Matas Labasauskas a écrit :
> Hello,
>
> by defaul
Hello,
by default Ticket Age is increasing from creation moment.
Would by nice to know, is it possible to get Ticket Age increasing only
during set (9:00 - 18:00) working hours?
thank you in advance,
--
Matas
___
OTRS mailing list: otrs - Webpage: htt
11 matches
Mail list logo