Bug 1826510
Summary: | Fix 'clear all filters' isn't consistently displaying on the filter toolbar (serach page only) | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Joe Caiani <jcaiani> |
Component: | Management Console | Assignee: | Joe Caiani <jcaiani> |
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.5 | CC: | aos-bugs, jokerman, yanpzhan |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: clear all filters had a bug in the upstream pf component
Consequence: clear all filters worked incorrectly in the search page
Fix: made upstream fix for clear all filters in toolbar filter component
Result: clear all filters successfully clears all filters now
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:29:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joe Caiani
2020-04-21 20:22:36 UTC
There is no 'clear all filters' for filter on Events page, should it be added, too? To keep consistent with other page, it's better to have "clear all filters" on event page, so assign back the bug. (In reply to Yanping Zhang from comment #4) > To keep consistent with other page, it's better to have "clear all filters" > on event page, so assign back the bug. Hi yanping, this bug was only for the pf toolbar component which is only in the search page as of now. The toolbar component story will be expanded in 4.6. For now, this is just for search toolbar. Thanks! Joe, thanks for your info. Now the "clear all filters" works on search page on 4.5 cluster with payload 4.5.0-0.nightly-2020-04-25-170442, so move the bug to Verified. 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/RHBA-2020:2409 |