Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 861190

Summary: [rfe] Additional clarification in tooltip for syntax requirement when searching for specific errata.
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: WebUIAssignee: Walden Raines <walden>
Status: CLOSED CURRENTRELEASE QA Contact: sthirugn <sthirugn>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: mmccune, sthirugn, walden
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 13:58:56 UTC Type: Bug
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: 1130651    
Attachments:
Description Flags
screenshot none

Description Corey Welton 2012-09-27 18:35:03 UTC
Description of problem:
When searching for the exact name of an errata, i.e., RHSA-2010:0842, user is required to put this in full quotes, i.e., "RHSA-2010:0842". That is fine, however, the tooltip for Errata in content search is not clear in noting that the quotes are required.

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


How reproducible:


Steps to Reproduce:
1. Sync a bunch of RHEL content (i.e., 6Server system rpms)
2. Content > Content Search > (Content type: Errata)
3. In the errata field, hover over the tooltip.  Note the indication for required text format (see forthcoming screenshot)
4. Enter an errata in the search field per the tooltips (i.e., RHSA-2010:0842) and hit return; view results
5. Enter an errata in the search field per the tooltips (i.e., "RHSA-2010:0842" -- with quotes) and hit return; view results
  
Actual results:
The former returns no results; the latter returns results.

Expected results:
I think it's perfectly fine for the former to return no results -- all those non alpha characters may well wreak havoc with search.  However, the tooltip makes no mention of the quotes being required.  We need to make sure that is clear in the tooltip.


Additional info:

Comment 1 Corey Welton 2012-09-27 18:48:41 UTC
Created attachment 618229 [details]
screenshot

Comment 3 Walden Raines 2014-11-04 19:23:57 UTC
This has been invalidated by the introduction of errata management as errata has been removed as an item from content search.

Comment 4 sthirugn@redhat.com 2015-03-17 15:05:30 UTC
Verified.

Search with autocomplete works fine in the new UI -> Content -> Errata - For example, I can search for id =  RHSA-2015:0674 and it worked fine.

Version Tested:
Satellite-6.1.0-RHEL-6-20150311.1

Comment 5 Bryan Kearney 2015-08-11 13:23:56 UTC
This bug is slated to be released with Satellite 6.1.

Comment 6 Bryan Kearney 2015-08-12 13:58:56 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.