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 1233135 - Search box is required on discovery rules page
Summary: Search box is required on discovery rules page
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-18 09:54 UTC by Sachin Ghai
Modified: 2019-09-26 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-03 07:23:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
search box should be there on discovery_rules page to filter out rules. (64.31 KB, image/png)
2015-06-18 09:54 UTC, Sachin Ghai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9021 0 None None None 2016-07-20 10:01:35 UTC
Foreman Issue Tracker 10961 0 None None None 2016-04-22 14:56:06 UTC

Description Sachin Ghai 2015-06-18 09:54:26 UTC
Created attachment 1040397 [details]
search box should be there on discovery_rules page to filter out rules.

Description of problem:
Currently UI doesn't show search box to filter out specific discover rule from a long list of rules.

Version-Release number of selected component (if applicable):
sat6.1 snap8 C2

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
no search box on discovery rules page

Expected results:
search box should be there to filter out rules.

Additional info:

Comment 2 Bryan Kearney 2015-06-30 17:57:46 UTC
Created redmine issue http://projects.theforeman.org/issues/10961 from this bug

Comment 3 Bryan Kearney 2017-03-22 20:24:27 UTC
There is a an upstream issue opened for this. We will no longer be tracking this downstream. If you believe this was closed in error please feel free to re-open with additional information.

Comment 4 Sachin Ghai 2017-04-28 14:44:51 UTC
Imagine if a user has created a more than 50 different rules then search is easier way to find to get the intended one. Moreover, we are also providing same search on other pages as well. 

So I think we should fix this in downstream too. we need search for out automation tests where we are creating/updating/deleting rules w/ different combinations. This is not required on urgent basis but its a intended feature and should be fixed.

Comment 5 Lukas Zapletal 2017-05-03 07:23:18 UTC
Sachin, we all understand that this is needed but so far not a single customer reported this and since there is technical difficulty with implementation due to limitations of scoped search and its double use on single page we decided not to implement it for now or for 6.3 release. We are tracking this upstream, let's not duplicate it in Bugzilla until necessary (customer case for example).


Note You need to log in before you can comment on or make changes to this bug.