Bug 1187304 - Content Hosts Bulk Actions errata search different than individual content hosts errata search.
Summary: Content Hosts Bulk Actions errata search different than individual content ho...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-29 17:54 UTC by Joe Giordano
Modified: 2023-09-14 02:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:58:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9180 0 None None None 2016-04-22 16:00:28 UTC

Description Joe Giordano 2015-01-29 17:54:32 UTC
Description of problem:

When the user selects Content Hosts, and picks a specific host they are presented with numerous tabs. Selecting Errata, the user is able to search in the field by entering characters. The search form automatically filters based on the characters entered. Bulk Actions have a very different behavior. 

Clicking the Bulk Actions in the top right of the screen, the user is taken to the bulk actions options. There is an Errata tab, when clicked the user is brought to a similar errata search screen that they did when they chose errata on individual content hosts. First select a few hosts from the left side Content Host listing. Errata should then be populated in the tabular view. If the user starts searching in the box above there are a few noticeable differences. The first difference is no auto filtering like the individual content hosts search. The second is that if the user presses the enter key, the search restarts and erases the content. The second noticeable thing is the need to qualify searches with the header, i.e. title:*tzdat* which is not the case with individual content host searches. 

Version-Release number of selected component (if applicable):
Satellite 6.0.7, Chrome 39.0.2171.95 or Firefox 34

How reproducible:
Constant

Steps to Reproduce:
1. Open Satellite and navigate to Hosts> Content Hosts
2. Select Bulk Actions in the top Right
3. Check a content hosts from the right and let the errata populate
4. Try searching by typing, it doesn't auto filter.
5. Press enter and the field is cleared. 


Expected results:
Results should mimic the same search if an individual content host is selected and the errata seached. Auto Filtering and not clearing the field when enter is pressed.

Comment 1 RHEL Program Management 2015-01-29 17:54:53 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Walden Raines 2015-01-30 20:42:30 UTC
Created redmine issue http://projects.theforeman.org/issues/9180 from this bug

Comment 4 Walden Raines 2015-02-24 14:27:40 UTC
Both of these searches now are using the same autocomplete style search.  These searches cannot use the autofiltering because we paginate the errata results (and thus any filter would only be filtering the results that were loaded on the page).

I'm moving this to ON_QA because I think the issue here is that they were using different style searches and that is no longer the case.

Comment 5 sthirugn@redhat.com 2015-03-17 21:05:29 UTC
Verified as per Comment 4 in Satellite-6.1.0-RHEL-6-20150311.1.

Joe, please reopen this bug or create a new bug if you are not okay with Comment 4 above and this comment.

Comment 6 Bryan Kearney 2015-08-11 13:32:27 UTC
This bug is slated to be released with Satellite 6.1.

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

Comment 8 Red Hat Bugzilla 2023-09-14 02:54:05 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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