1. Proposed title of this feature request  
           
Ability to have similar search functionality from Satellite 5 when searching for rpms/errata/package(s) in Satelite 6 for software channels/repositories

2. Who is the customer behind the request?  
    
Account: 3M (account# 941588)  
      
TAM customer: yes  
SRM customer: yes  
Strategic: yes  
      
3. What is the nature and description of the request?  

# Satellite 6 - current search view is limited when looking for *rpms
   
Satellite 6 -> Content Search -> Content = Select "Repositories" -> Click "Refresh Results" -> Default Org View -> Red Hat Enterprise Linux Server -> Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server -> Library tab - Click "Package #" 16,000+

Results for this view show all the package name and description only.

# Satellite 5 - the functionality that we are looking for

Satellite 5 -> Channels ->  Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) -> Packages tab

a.  Filter by Package Name 
b.  Ability to select a view by the first initial 
c.  Display up to 500 package names 
d.  Ability to select the package and view the package details

Add the 4 options above to Satellite 6.
      
4. Why does the customer need this? (List the business requirements here)  

Search functionality for rpms/errata/package(s) in Satellite 5 was easy and intuitive unlike in Satellite 6
      
5. How would the customer like to achieve this? (List the functional requirements here)  

See #3 above

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

Customer has a development environment that can test this

TAM also has a reproducer which follows the customers setup
      
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  

No
      
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

Satellite 6.3+
      
9. Is the sales team involved in this request and do they have any additional input?  

Yes
      
10. List any affected packages or components.  

NA
      
11. Would the customer be able to assist in testing this functionality if implemented?

Yes