AW: Fast delete tab for spam-tickets

Thanks, the Callbacks work fine. I also had an eye on the other cronjob rt-scripts.
I started with the rt-escalade cronjob. The first time I executed this file, all Tickets had the priority 10! :frowning: Should this script work?
Is the script still necessary? I’ve found a similar configuration the queue-config (InitialPriority, FinalPriority), but it didn’t work for itself.Von: [] Im Auftrag von Bob Goldstein
Gesendet: Donnerstag, 8. Juni 2006 15:37
An: Uli Stärk
Betreff: Re: [Rt-devel] Fast delete tab for spam-tickets

I’ve used the Callbacks from University of Kent:

(Scroll to the bottom for a description and download link.)

One of the features is a “delete” tab.


Due to massive spam in our rt-system I whish to add a new tab to the Ticket/Di
I’ve already found the file where the tabs are defined: Ticket/Elements/Tabs

There I’ve added the following code:
if ( $Ticket->CurrentUserHasRight(‘ModifyTicket’) ) {
$actions->{‘G’} = { title => loc(‘Spam’),
path => “Ticket/Update.html?Action=Spam&id=” . $id,

Now I want that if the user clicks on this link, the ticket is instantly marke
d as deleted so no further emails (like Ticked Resolved) are sent.

One possibility is to create a new ticket status (spam) that is equal to delet
ed. So if when the link is clicked, the ticket status is updated and the user
returns to the default-entry page of rt. But I think this is ways too complica
ted to code. So another (easier) possibility is to redirect the user to the Up
date.html page and pre-select the deleted-status.

Do you have another idea how to solve the spam problem?

Where can I find the script that handles the Aciton= GET-parameter in the Upda
te.html (2nd solution)?

List info:

Best Practical is hiring! Come hack Perl for us: