Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 842395 - Add informational icon for all search fields in Content Search page
Summary: Add informational icon for all search fields in Content Search page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-23 18:09 UTC by Og Maciel
Modified: 2017-04-24 14:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 17:37:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot (20.05 KB, image/png)
2012-07-23 18:09 UTC, Og Maciel 		no flags Details
View All

Description Og Maciel 2012-07-23 18:09:28 UTC 
Created attachment 599837 [details]
Screenshot

Description of problem:

Only the Errata and Packages search fields have an informational icon (the letter "i") explaining how to perform a search using the elasticsearch syntax. It would be nice to have a similar icon next to all the other search fields (i.e. Products and Repos).

Version-Release number of selected component (if applicable):

* candlepin-0.5.32-1.el6.noarch
* candlepin-tomcat6-0.5.32-1.el6.noarch
* katello-0.2.48-1.git.0.115520b.el6_3.noarch
* katello-all-0.2.48-1.git.0.115520b.el6_3.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.6-1.el6.noarch
* katello-cli-0.2.44-1.git.0.8873506.el6_3.noarch
* katello-cli-common-0.2.44-1.git.0.8873506.el6_3.noarch
* katello-common-0.2.48-1.git.0.115520b.el6_3.noarch
* katello-configure-0.2.31-1.git.0.f95c3fa.el6_3.noarch
* katello-glue-candlepin-0.2.48-1.git.0.115520b.el6_3.noarch
* katello-glue-foreman-0.2.48-1.git.0.115520b.el6_3.noarch
* katello-glue-pulp-0.2.48-1.git.0.115520b.el6_3.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-0.2.6-1.el6.noarch
* pulp-1.1.11-1.el6.noarch
* pulp-common-1.1.11-1.el6.noarch
* pulp-selinux-server-1.1.11-1.el6.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Justin Sherrill 2012-12-18 15:25:51 UTC 
So repos has a info box beside its search box.  The only boxes that do not have a info box are auto-complete fields which i'm not sure need one (at least not one that gives search syntax information).   I'm not sure what it would say other than 'start typing a product/repo name'.

Thoughts?
Comment 2 Mike McCune 2013-08-16 18:13:49 UTC 
getting rid of 6.0.0 version since that doesn't exist
Comment 3 Mike McCune 2014-03-18 17:37:48 UTC 
This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.
Note You need to log in before you can comment on or make changes to this bug.