Bug 168236 - Negation of boolean search doesn't stick
Summary: Negation of boolean search doesn't stick
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
URL:
Whiteboard:
: 203595 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-13 19:15 UTC by Suzanne Hillman
Modified: 2013-06-24 02:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-15 17:35:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Suzanne Hillman 2005-09-13 19:15:11 UTC
Description of problem:
If you are trying to do a report which includes negation of the boolean table,
the negation part gets dropped.

How reproducible:
Always

Steps to Reproduce:
1. Set up a report search, such as one involving RHEL and IT associated bugs
whose status changed in a time period, and whose boolean search on 'comments
changed after' is negated.
2. Run the report
3. The negation is lost.
  
Actual results:
The negation should be kept, and when one goes to edit the search, it should
show up there, too.

Expected results:
Negation kept, search ran as expected.

Additional info:

Comment 1 David Lawrence 2006-08-22 18:20:35 UTC
*** Bug 203595 has been marked as a duplicate of this bug. ***

Comment 2 David Lawrence 2008-09-16 16:53:30 UTC
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.

Comment 3 Suzanne Hillman 2008-09-16 17:27:25 UTC
This bug appears to still exist. The negation does show up in a 'edit search' view, but does not get reflected in the results.

Comment 4 David Lawrence 2008-12-01 19:52:52 UTC
Moving to ASSIGNED as this bug has been reverified and will need further investigation.

Comment 5 David Lawrence 2010-01-15 16:55:22 UTC
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and
therefore this bug will need to be re-verified against the new release. With
the updated code this bug may no longer be relevant or may have been fixed in
the new code. Updating bug version to 3.4.

Comment 6 Jan Kratochvil 2010-01-15 17:35:45 UTC
Verified as fixed.


Note You need to log in before you can comment on or make changes to this bug.