Well, that batch thing sounds good to me. And I agree to you, the 
stuff should go into the execute, but I did not had time to 
investigate exactly how to do that. Anyway, for the next couple of 
weeks I am assigned to another project, after that I will get back on 
this. So it can take a  while. But the batch thing sounds much better. 
So I think it will go into that direction.



Auke

Check that. What I'd like to see, and what I think would be more 
useful, is a revamped patch that lets you do batch actions on the 
results of any search (be it a query or a regular search - shouldn't 
matter).



You should be able to add a comment to all tickets, resolve them 
(handling one queue/type at a time, in batches), delete them, assign 
them, whatever.

Okay. I'd like to see a cleaner version of the patch; if it looks 
good, it can be committed.

Yes, I could see potential use of such a feature, though not in any 
environment I personally use. But if you hook Whups to a (public) 
support address, as mentioned on the mailing list, a way to mass 
delete tickets might make sense.

First of all, I'm not inclined to commit this. Would anyone else find 
it useful?



Second, this can't be committed as-is - you need to actually do the 
work in the execute() method of your form instead of polluting 
query.php with all of that unnecessary logic.

While it sounds very strange, it can be handy.

When you receive lots of tickets by e-mail (a normal situation in any 
company) you receive mostly a lot of spam. When the mailhandler patch 
(ticket 280) is in place those spam messages go to a seperate queue. 
Now u can easily search for all the tickets in a queue, save this 
search and from time to time execute the query, click the: "Delete all 
items" tab, confirm and bye bye spam tickets :). Also when you just 
want to delete large amount of (for example testing) tickets, u could 
use this patch, so even when it sounds strange, it could be handy.



Auke Bruinsma

ps. The patch is against CVS head.