I get the idea. I think it should work if I ever need to do forensic investigation. Thanks! On Tue, Nov 6, 2012 at 2:34 PM, Gerald Young wrote:

If they affected a ticket, Generic Agent will have used the API to make those changes, and therefore the ticket_history.create_time related to such change will be identical, or very close, to the time of Generic Agent action.

Sample query that gives you a bit of detail on what happened: SELECT ticket.tn, ticket_history.name, ticket_history_type.name, ticket_history.create_time FROM ticket_history LEFT JOIN ticket ON ticket.id=ticket_history.ticket_id LEFT JOIN ticket_history_type ON ticket_history_type.id = ticket_history.type_id WHERE ticket_history.create_time between "2012-07-07 14:50:00" AND "2012-07-07 14:54:00"

If you just want ticket numbers, remove the other columns and append GROUP BY ticket.tn

On Tue, Nov 6, 2012 at 3:28 AM, Bogdan Iosif wrote:

...

Hi,

I have a couple of db Generic Agent jobs (configured through admin frontend GUI) and I would like to know the tickets affected by these jobs on each execution.

Looking in otrs.log I can see one line for each job execution, like this:

[Tue Nov 6 10:20:02 2012][Notice][Kernel::System::GenericAgent::JobRun] Run GenericAgent Job '...' from db.

I would like to know, at least, the ticket numbers for the affected tickets. Is there any way to achieve this with configurations?

Thanks, Bogdan

--------------------------------------------------------------------- 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

--------------------------------------------------------------------- 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