Consistent deletion of tickets

Hello, I have a question: After a testperiod where we tested some configuration issues, our system now has gone live. I would really like to delete all the test tickets now, so that they do not appear in the ticket search or in the statistics. I know that for consistency reasons deletion normally is not possible in otrs. Exists a common approach how to delete tickets in a consistent way? Is it sufficient to delete the tickets entrys in the ticket and in the history table? Thanks in advance, Hannes Riechmann

Hannes Riechmann wrote:
I have a question: After a testperiod where we tested some configuration issues, our system now has gone live. I would really like to delete all the test tickets now, so that they do not appear in the ticket search or in the statistics. I know that for consistency reasons deletion normally is not possible in otrs. Exists a common approach how to delete tickets in a consistent way? Is it sufficient to delete the tickets entrys in the ticket and in the history table?
You can delete tickets through OTRS. We have a Junk queue and a GenericAgent job that deletes all tickets in this queue every five minutes. Works just fine. Nils Breunese.

--On Sunday, January 20, 2008 6:23 PM +0100 "Nils Breunese (Lemonbit)"
You can delete tickets through OTRS. We have a Junk queue and a GenericAgent job that deletes all tickets in this queue every five minutes. Works just fine.
Nils, that's great to know, thank you. We don't see tickets getting deleted from the junk queue. They just collect there. Do we have to do something to activate that? Should there be a CRON job for it? Thanks...

Jim Archer wrote:
--On Sunday, January 20, 2008 6:23 PM +0100 "Nils Breunese (Lemonbit)"
wrote: You can delete tickets through OTRS. We have a Junk queue and a GenericAgent job that deletes all tickets in this queue every five minutes. Works just fine.
Nils, that's great to know, thank you. We don't see tickets getting deleted from the junk queue. They just collect there. Do we have to do something to activate that? Should there be a CRON job for it?
Like I said, we have a GenericAgent job that runs every couple minutes and deletes the tickets in the Junk queue. That is like a cron job, except it's not a cron job, but a GenericAgent job in OTRS. See 'Executing automated jobs with the GenericAgent' in the docs: http://doc.otrs.org/2.2/en/html/x1149.html Nils Breunese.

Oh, I understand now, thanks Nils.
--On Sunday, January 20, 2008 11:05 PM +0100 "Nils Breunese (Lemonbit)"
Like I said, we have a GenericAgent job that runs every couple minutes and deletes the tickets in the Junk queue. That is like a cron job, except it's not a cron job, but a GenericAgent job in OTRS. See 'Executing automated jobs with the GenericAgent' in the docs: http://doc.otrs.org/2.2/en/html/x1149.html

That works great. Thanks! Nils Breunese (Lemonbit) wrote:
Hannes Riechmann wrote:
I have a question: After a testperiod where we tested some configuration issues, our system now has gone live. I would really like to delete all the test tickets now, so that they do not appear in the ticket search or in the statistics. I know that for consistency reasons deletion normally is not possible in otrs. Exists a common approach how to delete tickets in a consistent way? Is it sufficient to delete the tickets entrys in the ticket and in the history table?
You can delete tickets through OTRS. We have a Junk queue and a GenericAgent job that deletes all tickets in this queue every five minutes. Works just fine.
Nils Breunese. _______________________________________________ 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/
participants (3)
-
Hannes Riechmann
-
Jim Archer
-
Nils Breunese (Lemonbit)