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 1325450 - Content View : Update puppet module filter to become a search
Summary: Content View : Update puppet module filter to become a search
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-08 20:47 UTC by Brad Buckingham
Modified: 2019-09-26 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-26 01:05:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Satellite 6.2: Content View: Puppet module search input (118.96 KB, image/png)
2016-08-26 01:04 UTC, Brad Buckingham 		no flags Details
Satellite 6.2: Content View: Puppet module search options (120.79 KB, image/png)
2016-08-26 01:05 UTC, Brad Buckingham 		no flags Details
View All

Description Brad Buckingham 2016-04-08 20:47:49 UTC 
Description of problem:

The interface for adding puppet modules to a content view (in the UI) utilizes a filter of loaded puppet modules instead of allowing the user to search for available puppet modules.  This makes it very difficult locate and add puppet modules to a content when working with a lot of puppet modules (e.g. puppet forge).

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

satellite-6.2.0-7.0.beta.el7sat.noarch
tfm-rubygem-katello-3.0.0.15-1.el7sat.noarch


How reproducible:
Always

Steps to Reproduce:
1. Create a puppet repo that points to puppet forge (https://forge.puppetlabs.com)
2. Sync the repo
3. Create a content view
4. go to Content -> Content Views -> [mynewview] -> Puppet Modules
5. click 'Add New Module'

Actual results:

Observe the the input box is a "Filter...".  As a result, I have to scroll until I locate the module that I would like to add to the content view.

Expected results:

The "Filter..." should really be a "Search..." that will allow me to leverage the power of scoped search on the server-side to help me locate the puppet module.

Additional info:

Related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1324330
Comment 2 Sebastian Hetze 2016-04-25 12:39:04 UTC 
This is not an enhancement but a regression. In Sat6.1 this lookup works.
Comment 5 Brad Buckingham 2016-08-26 01:04:09 UTC 
In Satellite 6.2 GA, this is now indeed a search.  Attaching 2 screenshots to illstrate and closing the bugzilla.
Comment 6 Brad Buckingham 2016-08-26 01:04:47 UTC 
Created attachment 1194177 [details]
Satellite 6.2: Content View: Puppet module search input
Comment 7 Brad Buckingham 2016-08-26 01:05:29 UTC 
Created attachment 1194178 [details]
Satellite 6.2: Content View: Puppet module search options
Note You need to log in before you can comment on or make changes to this bug.