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 1614906 - Search bar assuming dropdown causes issues when typing in partial names
Summary: Search bar assuming dropdown causes issues when typing in partial names
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: 6.6.0
Assignee: Walden Raines
QA Contact: vijsingh
URL:
Whiteboard:
Depends On:
Blocks: 1650655 1650656 1650660
TreeView+ depends on / blocked
 
Reported: 2018-08-10 17:00 UTC by sandeep mutkule
Modified: 2019-10-22 19:47 UTC (History)
9 users (show)

Fixed In Version: tfm-rubygem-katello-3.12.0.16-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1650655 1650656 1650660 (view as bug list)
Environment:
Last Closed: 2019-10-22 19:47:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26792 0 'Normal' 'Closed' 'Search bar assuming dropdown causes issues when typing in partial names' 2019-12-03 17:49:59 UTC

Description sandeep mutkule 2018-08-10 17:00:35 UTC 
1. Proposed title of this feature request
Ans: Improve search interface in Satellite


2. What is the nature and description of the request?
Ans: There are multiple deficiencies in the interface that need to be addressed because they cause unexpected behavior.


3. Why does the customer need this? (List the business requirements here)
Ans: Overall usability of the product is impacted.

4. How would the customer like to achieve this? (List the functional requirements here)
Ans: - It should be possible to increase the number of entries shown on a page beyond 100 without manually editing the URL.
     - If there is a reason that Content Hosts and All Hosts have different information, this information needs to be documented, and some location (either, or a third) should have the information from both of the
       current interfaces.
     - It should be possible to search by Errata number in the Errata interface. Surprisingly, this is not possible in the current version.
     - It should be immediately evident whether the interface is still waiting for search results, or if it has returned limited (or no) content.
     - When updating the search parameters while a search is in process, the current behavior triggers on the completion of the search - which wipes out the updated search parameters. Worse, this definitely happens
       when performing the initial "empty" search. That is, when you go to a page and start definining a search, it will wipe out the search criteria. And if you successfully run a search before the "empty" search
       completes, you instead get the initial results and not your customized results. (I preseume the search was still submitted and created load on the system, although you will never be able to see the output.)
     - Searching on an IP address should match a subnet that includes that address. Currently it is a string based match, so 128.129.10.10 would not match the subnet definition 128.128.0.0/12 that properly includes that IP.
     - The search bar accepts suggestions from the drop-down list by default - this can easily cause incorrect behavior. This can be reliably recreated when searching errata for a package name.
       If you put in "package ~ " and a substring that matches the beginning of a package, hitting Enter will cause the first match to be used. The expected behavior is to require one of the matches to be selected with the
       mouse or arrow keys. After that, hitting Enter should run the current search exactly as typed.

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Ans: NA
Comment 1 Marek Hulan 2018-08-13 06:43:20 UTC 
This needs to be triaged to separate bugs. E.g. searching by erratas is not related to pagination and would be implemented separately. Some of these may already be tracked as existing BZs
Comment 2 Brad Buckingham 2018-08-14 17:34:59 UTC 
Hi Sandeep,

Can you submit multiple RFEs as mentioned in comment 1?
Comment 3 sandeep mutkule 2018-10-29 15:02:51 UTC 

@Brad 

Sorry but I am not aware of such RFEs, but I will try to search and will let you know If I found any.
Comment 7 Bryan Kearney 2018-11-16 18:49:24 UTC 
Splitting apart this bug:

Ans: - It should be possible to increase the number of entries shown on a page beyond 100 without manually editing the URL.

[bk] Tracking this as https://bugzilla.redhat.com/show_bug.cgi?id=1650655

     - If there is a reason that Content Hosts and All Hosts have different information, this information needs to be documented, and some location (either, or a third) should have the information from both of the
       current interfaces.

[bk] We are tracking this as an interal requirement for feture deliver.


     - It should be possible to search by Errata number in the Errata interface. Surprisingly, this is not possible in the current version.

[bk] I see id as the searchable field (e.g. id =   RHBA-2018:1276) This should support the use case you are asking for.

     - It should be immediately evident whether the interface is still waiting for search results, or if it has returned limited (or no) content.

[bk] Tracking this as https://bugzilla.redhat.com/show_bug.cgi?id=1650656

     - When updating the search parameters while a search is in process, the current behavior triggers on the completion of the search - which wipes out the updated search parameters. Worse, this definitely happens
       when performing the initial "empty" search. That is, when you go to a page and start definining a search, it will wipe out the search criteria. And if you successfully run a search before the "empty" search
       completes, you instead get the initial results and not your customized results. (I preseume the search was still submitted and created load on the system, although you will never be able to see the output.)

[bk] Tracking this as https://bugzilla.redhat.com/show_bug.cgi?id=1650660

     - Searching on an IP address should match a subnet that includes that address. Currently it is a string based match, so 128.129.10.10 would not match the subnet definition 128.128.0.0/12 that properly includes that IP.

[bk] I do not see us implementing this.

     - The search bar accepts suggestions from the drop-down list by default - this can easily cause incorrect behavior. This can be reliably recreated when searching errata for a package name.
       If you put in "package ~ " and a substring that matches the beginning of a package, hitting Enter will cause the first match to be used. The expected behavior is to require one of the matches to be selected with the
       mouse or arrow keys. After that, hitting Enter should run the current search exactly as typed.
Comment 8 Bryan Kearney 2018-11-16 18:50:24 UTC 
For clarity, this bug now tracks onlu;

     - The search bar accepts suggestions from the drop-down list by default - this can easily cause incorrect behavior. This can be reliably recreated when searching errata for a package name.
       If you put in "package ~ " and a substring that matches the beginning of a package, hitting Enter will cause the first match to be used. The expected behavior is to require one of the matches to be selected with the
       mouse or arrow keys. After that, hitting Enter should run the current search exactly as typed.
Comment 10 Marek Hulan 2019-02-12 17:59:57 UTC 
With the new scope, I think this now falls under webui. Ron, is the new react implementation already working this way? Would it be possible to adapt it?
Comment 11 Ron Lavi 2019-02-12 19:54:37 UTC 
AFK right now, but there have been some UX changes since this was opened, though the API requests and responses remained the same.
I will test this behaviors first thing tomorrow.
Comment 12 Ron Lavi 2019-02-14 13:40:49 UTC 
With the new SearchBar implementation on Foreman,

this behavior mentioned above doesn't happen anymore.

Instead of choosing the first result, hitting 'Enter' will search the query which is already inside the input, for example:

---------------

Typing in: 'n' ==> receiving the result 'name' ==> selecting it by mouse / key Arrows + Enter or Tab ==> 'name' will appear in the input

==> getting results of 'name' with equality Operators ==> selecting one of the results, e.g. 'name = ' ==> 'name = ' will appear in the input ==> 

==> getting a list of all suitable results ==> selecting 'name = some-host' ==> input will contain now 'name = some-host' ==> 

==> getting results of the search query with operators => I don't need the operators search so I hit Enter / press the search button ==> 

==> now the table or another view will get updated with my search query: 'name = some-host'

---------------
Comment 13 Walden Raines 2019-02-14 14:10:47 UTC 
Can we close this as resolved upstream per comment#12?
Comment 15 Walden Raines 2019-02-18 19:43:22 UTC 
Moving to ON_QA for verification.
Comment 20 Walden Raines 2019-05-14 13:23:03 UTC 
I'll have a look.  It's possible that this is fixed in the react version of the dropdown but not the legacy katello angular version.
Comment 21 Walden Raines 2019-05-14 13:25:19 UTC 
Created redmine issue https://projects.theforeman.org/issues/26792 from this bug
Comment 22 Walden Raines 2019-08-15 14:23:18 UTC 
This has been merged with 9b403dd8c9844d9fbd25212ced0b3b22dd43c6d1, not sure why the script didn't pick it up.

https://github.com/Katello/katello/pull/8234
Comment 24 vijsingh 2019-08-27 06:41:56 UTC 
ON_QA Verified

@Satellite 6.6.0 snap 17.0

Steps/Observation:

1) It works as  expected errata(Content => Errata => in Search bar put 'package ~' and selected with the mouse or arrow keys)
"""
put in "package ~ " and selected with the mouse or arrow keys. After that, hitting Enter run the current search exactly as typed.
"""


2) It works as expected for "Hosts  => All Hosts"(Instead of choosing the first result, hitting 'Enter' will search the query which is already inside the input) for example:
"""
Typing in: 'n' ==> receiving the result 'name' ==> selecting it by mouse / key Arrows + Enter or Tab ==> 'name' will appear in the input

==> getting results of 'name' with equality Operators ==> selecting one of the results, e.g. 'name = ' ==> 'name = ' will appear in the input ==> 

==> getting a list of all suitable results ==> selecting 'name = some-host' ==> input will contain now 'name = some-host' ==> 

==> getting results of the search query with operators => I don't need the operators search so I hit Enter / press the search button ==> 

==> now the table or another view will get updated with my search query: 'name = some-host
"""
Comment 25 Bryan Kearney 2019-10-22 19:47:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3172
Note You need to log in before you can comment on or make changes to this bug.