Bug 1525237

Summary: Tag filter missing from Physical Infrastructure Topology view
Product: Red Hat CloudForms Management Engine Reporter: Jerome Marc <jmarc>
Component: UI - OPSAssignee: Felipe <felipe.diogenes13>
Status: CLOSED ERRATA QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.0CC: cpelland, gblomqui, hkataria, jhardy, mpovolny, obarenbo, rbrown4, simaishi, smallamp, tstoddard
Target Milestone: GA   
Target Release: 5.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-07 23:00:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Lenovo Target Upstream Version:
Description Flags
Physical Infrastructure Topology View with no Tag filtering none

Description Jerome Marc 2017-12-12 20:52:17 UTC
Created attachment 1366950 [details]
Physical Infrastructure Topology View with no Tag filtering

Description of problem:
The Topology view for physical infrastructure does not allow users to filter out tags on the graph. All other topology views let you do that. It should be added to the physical infrastructure topology view.

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

How reproducible:

Steps to Reproduce:
1. Navigate to Compute > Physical Infrastructure > Topology

Actual results:
Topology view does not allow to filter out tags

Expected results:
Topology view should display a tag filter like all other topology views.

Additional info:

Comment 2 tstoddard 2018-02-20 18:30:31 UTC
2/20/2018: Moving to 6.0.0 release.

Comment 3 Rodney H. Brown 2018-10-17 13:48:08 UTC
Fixed in PR  https://github.com/ManageIQ/manageiq-ui-classic/pull/4743 upstream.  Requires backport for inclusion in the 5.10 stream.

Comment 4 Rodney H. Brown 2018-11-13 20:07:55 UTC
Verified with build

Comment 5 errata-xmlrpc 2019-02-07 23:00:45 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.