Closed
Bug 292753
Opened 20 years ago
Closed 19 years ago
"Does Not Equal" fails to work in Boolean Charts
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: marc.pierre, Unassigned)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) Build Identifier: Equals to a string ==> works perfectly Does not equal a string ==> does not work at all With the exact same string I can create a report with the EQUALS a string but when I try to exclude (does not equal) that exact same string my results are not any different... it excludes nothing even though the string is present. Reproducible: Always
Comment 1•20 years ago
|
||
Marc, in order to reproduce this, can you please put the URL of your faulty search into the URL field of this bug? When you run your search, the "Edit search" link below the search results contains the URL I'm looking for.
Updated•20 years ago
|
Summary: Advanced Query → "Does Not Equal" fails to work in Boolean Charts
Comment 2•20 years ago
|
||
Also, please include the version number
| Reporter | ||
Comment 3•20 years ago
|
||
Bugzilla Version 2.16.5
| Reporter | ||
Comment 4•20 years ago
|
||
http://bugzilla/buglist.cgi? short_desc_type=allwordssubstr&short_desc=&component=PCIS+Regression&long_desc_t ype=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug _status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&emailass igned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&em ailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin =&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=Marc&newqueryna me=&order=Reuse+same+sort+as+last+time&field0-0-0=longdesc&type0-0- 0=notregexp&value0-0-0=pierre.* Even using a simple value not = to a string instead of the REGEXP it does notwork.... nothing with DOES NOT = works using a COMMENT FIELD
Comment 5•20 years ago
|
||
Oh, 2.16 -- that's pretty old. There have also been a few 2.16.x releases since yours. You definitely want to upgrade to 2.18, if you can. If this bug affects only 2.16, we probably won't be fixing it, because 2.16 is in deep maintenance mode.
Version: unspecified → 2.16.5
Comment 6•20 years ago
|
||
I fixed a large number of boolean chart issues in 2.19 as well.. You can try this in 2.19 (bugzilla-tip) at http://landfill.bugzilla.org/ as well as getting access to the other versions.
Comment 7•19 years ago
|
||
The reason you get the same results is that you are querying comments, and if a comment doesn't contain the string you want to exclude but another one has, it will be included in both cases, depending on which one you are looking for. I did some tests on both 2.18.4 and 2.21.1, using "equals", "doesn't equal", "match regexp", "doesn't match regexp" and either the status whiteboard or comments. Results are the ones I expected. So WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•