Bug 740888

Summary:	[ipa webui] Searching will find an object for a field/setting that matched this criteria, but is not displayed
Product:	Red Hat Enterprise Linux 6	Reporter:	Namita Soman <nsoman>
Component:	ipa	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED WONTFIX	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	dpal, jgalipea, mkosek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-27 07:43:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	756082

Description Namita Soman 2011-09-23 16:21:40 UTC

Description of problem:
In HBAC Rules. search for the leter 'm', and allow_all will be listed, because its description contains 'from'. But the page doesn't display description, and so the user is left confused as to why this rule is displayed. 

Or if a rule is added, and it applies to a host whose name contains 'm', then the search will find this rule too.

Search should be limited to the fields that are displayed to avoid confusion.

Version-Release number of selected component (if applicable):
ipa-server-2.1.1-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Add and edit HBAC rule - test
2. Go to its Accessing section, and click to Add a Host
3. Add a host - say - example.testrelm
4. Go back to HBAC Rules page, and search for the letter 'm'
  
Actual results:
the rule 'test' is listed

Expected results:
the rule 'test' should not have matched the criteria


Additional info:

Comment 2 Rob Crittenden 2011-09-23 17:33:45 UTC

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1855

Comment 4 Martin Kosek 2012-02-22 16:10:30 UTC

There were some further discussions about this issue on both CLI and WebUI side and we came to a common agreement. We think we do the right thing with searching for given term ('m' in your case) in all object's default attributes. Even if some field is not shown (in WebUI) that does not necessarily mean that user would not want to search the term in such field.

Talking specifically about description field, user could have his custom data in such field and would not like if he suddenly can't search in it. That would sound more like a regression IMO. I plan to close this bug as WONTFIX if nobody protests.

Comment 5 Martin Kosek 2012-02-27 07:43:21 UTC

Closing the BZ as WONTFIX.