Bug #9440
closedSearch vs Filter inconsistencies in how search fields are handled throughout the UI
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1192196
Description of problem:
There seems to be a few different variations of search and filter bars across the Satellite UI. Most places we have a field that says "Filter..." in it, and has a Search button. Some pages have a field that says "Search..." in it, with a magnifying glass as the button, and no text. Other pages that have secondary search/filters bars have fields that just say "Filter" (no ellipses), and no button, you have to hit enter.
For example, on the Products page, we have a "Search..." bar up top, with a "Filter" bar for the Yum Repo Discovery Results.
All of the pages that don't live underneath the Content tab seem to use a "Filter..." bar, while the pages under Content instead have "Search..." bars. This is further convoluted by the fact that the Filter fields use a Search button, while the Search fields don't have any button text, and there are other Filter fields that don't have a button at all.
It would be nice if we were more consistent in how we handled searching/filtering.
Version-Release number of selected component (if applicable):
6.0.6
Updated by Dominic Cleal about 10 years ago
- Project changed from Foreman to Katello
- Assignee deleted (
Ohad Levy) - Triaged set to No
Updated by Eric Helms about 10 years ago
- Translation missing: en.field_release set to 31
- Triaged changed from No to Yes
Updated by Eric Helms about 10 years ago
- Translation missing: en.field_release deleted (
31)
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release set to 86
Updated by Eric Helms about 9 years ago
- Translation missing: en.field_release changed from 86 to 114
Updated by John Mitsch over 5 years ago
- Status changed from New to Rejected
- Target version deleted (
Katello Backlog)
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.