|
History
| Log In
|
|
|
|
that's fine. I've always said that better reporting and search functionality would require getting outside of the box, that is, getting outside of the current left-nav box that the filters are currently displayed in.
a multi-stage wizard would be fine. as would something that took up the full horizontal width of the screen but was hidden (like with the trick you do on error pages) when results are displayed. Hi,
It is not currently possible to create an exclusion in a search request. This issue has already been raised in JRA-1635. Thanks, Definitly a must for for search.
In the interim, perhaps it's possible to document a syntax for these searches and use it in the "Text Search". For example: Field:Status Open Or: !Field:Status Open I see as essential to have this working ofr custom fields as well. Thanks. A power tool might be handy. This could be a seperate page on the site, something that would allow complex filters to be created, saved and shared via the current Manage Filters page.
Whatever the mechanism, the "not" or "exclude" functionality is a must.
I'm using a custom field type multi checkbox. For this field I need to search via NOT.
There is more the request which value is NOT checked than checked. Please vote for JIRA-1560; that seems to be where all the votes are being pooled for this.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
"not" qualifier on fields for searching
JRA-699), so this will likely happen then.