Hi, Alexander Scholler wrote:
Your modification really looks good as far as I can decide! I would appreciate it being included in further releases.
thanks! I'm not sure if my CVS access got revoked since I was idle in the last two years, otherwise I'd include it myself. Martin, am I still active?
The SQL-syntax "interval" isn't SQL-standard but MySQL-specific - am I right?
actually I use Postgresql. I'm not sure whether it's standard or not.
Your approach to use change_time within Kernel::System::Ticket::TicketSearch is really interesting.
The question is: When is change_time changed?
As far as I could see, it is change within Kernel::System::Ticket through this subs: SetCustomerData TicketFreeTextSet PendingTimeSet LockSet StateSet ResponsibleSet PrioritySet TicketCreate
So many (all?) changes on ticket-properties result in a refreshed change_time. But e.g. if you just add a note to a ticket, the change_time remains.
I forgot something: --- GenericAgent.pm.orig 2007-02-27 15:26:07.000000000 +0100 +++ GenericAgent.pm 2007-02-27 15:26:43.000000000 +0100 @@ -400,6 +400,13 @@ my $Ticket = "($Param{TicketNumber}/$Param{TicketID})"; + # -- + # update change_time + # -- + # db update + my $SQL = "UPDATE ticket SET change_time = NOW() WHERE id = $Param{TicketID} "; + $Self->{DBObject}->Do(SQL => $SQL); # -- # move ticket # -- basically I'm taking care of 'idle' tickets and do something. Everytime I moarn about an untouched ticket I also update the change time so that I can moarn again in x days.
This could also be a problem for you? My approach (can be found on mailing-list (german or english?)) notices the added note.
-- Regards, Wiktor Wodecki net mobile AG, Zollhof 17, 40221 Duesseldorf, Germany 923B DCF8 070C 9FDD 5E05 9AE3 E923 5A35 182C 9783