Roundup Tracker - Issues

Issue 678900

classification
Title: Ability to specify non-matching criteria in filters/searches
Type: rfe Severity: normal
Components: Interface Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: richard Nosy List: ajaksu2, richard
Priority: normal Keywords:

Created on 2003-02-02 04:14 by anonymous, last changed 2009-04-06 04:23 by ajaksu2.

Messages
msg3158 Author: [hidden] (anonymous) Date: 2003-02-02 04:14
It would be nice to be able to select
issues by attributes that the 
issues
do not have. E.G.

 list issues that do not have the 
word hardware in them

or 

 list issues that do not have 
the status dead.

Granted the last can be done by crafting 
a
request that includes all other possibilities,
but multi-
element selections aren't available
on the current web 
interface.


-- rouilj
msg3159 Author: [hidden] (richard) Date: 2003-10-10 04:28
Logged In: YES 
user_id=6405

Implicitly matching empty strings is also desired. 
msg3683 Author: [hidden] (ajaksu2) Date: 2009-04-06 04:23
I'm working on a way to pass 'class:property' pairs as keys to the
'ignore' parameter of indexer.search[1], so the user can exclude some
properties from 'All text' searches.

While it's not exactly about "non-matching criteria in filters", it
makes me think that this RFE is implementable in
templating.HTMLRequest.[batch|_post_init] (as opposed to building
support for negative filterspecs in classes).

I'll give this a try soon :)

[1] http://psf.upfronthosting.co.za/roundup/meta/issue262
History
Date User Action Args
2009-04-06 04:23:42ajaksu2setmessages: + msg3683
2009-02-20 02:02:57ajaksu2setnosy: + ajaksu2
2003-02-02 04:14:29anonymouscreate