Bug 823788 - the search function doesn's return right results
Summary: the search function doesn's return right results
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Query/Bug List
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 4.2-1
Assignee: Simon Green
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: BZ42
TreeView+ depends on / blocked
 
Reported: 2012-05-22 07:29 UTC by Tony Fu
Modified: 2018-12-09 06:29 UTC (History)
2 users (show)

Fixed In Version: 4.2.1-1.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-22 13:13:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Tony Fu 2012-05-22 07:29:57 UTC
Description of problem:

The advanced search function in bz 4.2 doesn't return right results as it did in previous version.  Therefore, some existing saved queries don't work on current bz.


How reproducible:
always

Steps to Reproduce:
1.take https://bugzilla.redhat.com/show_bug.cgi?id=823092 as an example, it has "needinfo? (hwcert-reviewers)" flag set and user who is in one of the following groups - amd, dell,hp, Red Hat Employee, etc can access this bug
2. Log in bz as a user who is in "Red Hat Employee" group but not in any vendor groups (like amd, dell, hp, etc)
3.Use advance search page to search bug with needinfo flag set to "hwcert-reviewers"
  
Actual results:
the bug #823092 doesn't in the result list


Expected results:
the bug #823092 should be in the result list


Additional info:
It seems to me that the "OR group" function doesn't work for search function in new bz.  When deciding a user's permission to access a bug, it checks if the user is in ANY of the pre-selected groups.  While when deciding a user's permission to search a bug, it checks if the user is in ALL of the pre-selected groups.

Comment 1 Simon Green 2012-05-22 13:13:47 UTC
Good spotting on this one Tony. That was a major issue. It will be fixed in the next release.

  -- simon

Comment 3 Simon Green 2012-05-22 21:25:42 UTC
This change is now live.


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