<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Delete the resulting tickets of a query.</title> 
  <pubDate>Fri, 10 Apr 2026 19:28:22 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/1612</link> 
  <atom:link rel="self" type="application/rss+xml" title="Delete the resulting tickets of a query." href="https://bugs.horde.org/ticket/1612/rss" /> 
  <description>Delete the resulting tickets of a query.</description> 
 
   
   
  <item> 
   <title>While it sounds very strange, it can be handy.

When you rec</title> 
   <description>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: &quot;Delete all items&quot; 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.</description> 
   <pubDate>Wed, 23 Mar 2005 09:20:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/1612#t6567</link> 
  </item> 
   
  <item> 
   <title>First of all, I&#039;m not inclined to commit this. Would anyone </title> 
   <description>First of all, I&#039;m not inclined to commit this. Would anyone else find it useful?



Second, this can&#039;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.</description> 
   <pubDate>Wed, 23 Mar 2005 17:26:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/1612#t6582</link> 
  </item> 
   
  <item> 
   <title>Yes, I could see potential use of such a feature, though not</title> 
   <description>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.</description> 
   <pubDate>Wed, 23 Mar 2005 22:03:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/1612#t6588</link> 
  </item> 
   
  <item> 
   <title>Okay. I&#039;d like to see a cleaner version of the patch; if it </title> 
   <description>Okay. I&#039;d like to see a cleaner version of the patch; if it looks good, it can be committed.</description> 
   <pubDate>Wed, 23 Mar 2005 22:05:18 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/1612#t6589</link> 
  </item> 
   
  <item> 
   <title>Check that. What I&#039;d like to see, and what I think would be </title> 
   <description>Check that. What I&#039;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&#039;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.</description> 
   <pubDate>Wed, 23 Mar 2005 22:06:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/1612#t6590</link> 
  </item> 
   
  <item> 
   <title>Well, that batch thing sounds good to me. And I agree to you</title> 
   <description>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</description> 
   <pubDate>Thu, 24 Mar 2005 08:37:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/1612#t6603</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
