6.0.0-alpha12
6/11/25

[#1612] Delete the resulting tickets of a query.
Summary Delete the resulting tickets of a query.
Queue Whups
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester a.bruinsma (at) tools4ever (dot) com
Created 03/23/2005 (7385 days ago)
Due
Updated 11/08/2008 (6059 days ago)
Assigned 03/23/2005 (7385 days ago)
Resolved 11/08/2008 (6059 days ago)
Milestone
Patch No

History
11/08/2008 05:17:57 AM Chuck Hagenbuch State ⇒ Rejected
 
06/23/2005 11:33:46 PM Chuck Hagenbuch State ⇒ Stalled
 
03/24/2005 08:37:54 AM a (dot) bruinsma (at) tools4ever (dot) com Comment #6 Reply to this comment
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
03/23/2005 10:06:53 PM Chuck Hagenbuch Comment #5 Reply to this comment
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.
03/23/2005 10:05:18 PM Chuck Hagenbuch Comment #4 Reply to this comment
Okay. I'd like to see a cleaner version of the patch; if it looks 
good, it can be committed.
03/23/2005 10:03:37 PM Jan Schneider Comment #3 Reply to this comment
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.
03/23/2005 05:26:54 PM Chuck Hagenbuch Taken from Chuck Hagenbuch
 
03/23/2005 05:26:45 PM Chuck Hagenbuch Comment #2
State ⇒ Feedback
Reply to this comment
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.
03/23/2005 10:07:05 AM Jan Schneider Assigned to Chuck Hagenbuch
State ⇒ Assigned
 
03/23/2005 09:20:38 AM a (dot) bruinsma (at) tools4ever (dot) com Comment #1
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Delete the resulting tickets of a query.
Queue ⇒ Whups
New Attachment: query.php.patch Download
State ⇒ New
Reply to this comment
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.

Saved Queries