Bug 793646 (JBEPP-725) - Provide a button/icon to reset the search string
Summary: Provide a button/icon to reset the search string
Keywords:
Status: CLOSED DUPLICATE of bug 793647
Alias: JBEPP-725
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.0.x
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard: EPP_6_0_0_Candidate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-10 15:44 UTC by Martin Weiler
Modified: 2018-11-14 16:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 793647 (view as bug list)
Environment:
Last Closed: 2012-09-03 11:27:16 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-725 0 Major Closed Provide a button/icon to reset the search string 2012-09-06 22:49:07 UTC

Description Martin Weiler 2010-12-10 15:44:30 UTC
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000005STFx
project_key: JBEPP

When I first click on the User Management, it does show the full list of users from LDAP. But after searching some user entry if I click on the User Management again, it does not render the full user list. The only way to get the full user list is to clear the entry in the search box and click the Search Icon. 

From the usability standpoint of view, I think clicking again on the User Management should clear the search entry and render the full list of users.

If this can't be changed because of the current design then at least there should be a way to clear the search criteria. 

The same applies to other lists which offer search functionality, such as in the Page Management.

Comment 1 Thomas Heute 2012-01-13 12:57:03 UTC
Labels: Added: EPP_6_0_0_Candidate


Comment 2 Thomas Heute 2012-09-03 11:27:16 UTC

*** This bug has been marked as a duplicate of bug 793647 ***


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