Bug 1507915 - [Regression] Security groups UI is not displayed correctly
Summary: [Regression] Security groups UI is not displayed correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Gilles Dubreuil
QA Contact: Dave Johnson
URL:
Whiteboard: openstack
Depends On:
Blocks: 1518026
TreeView+ depends on / blocked
 
Reported: 2017-10-31 12:45 UTC by Marek Aufart
Modified: 2018-06-21 21:21 UTC (History)
9 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1518026 (view as bug list)
Environment:
Last Closed: 2018-06-21 21:21:12 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marek Aufart 2017-10-31 12:45:25 UTC 
Description of problem:

There was an UI refactoring, which broke https://bugzilla.redhat.com/show_bug.cgi?id=1487103, so Security groups UI is not displayed correctly.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Marek Aufart 2017-10-31 12:47:00 UTC 
https://github.com/ManageIQ/manageiq-ui-classic/pull/2543
Comment 3 Dave Johnson 2017-10-31 13:03:20 UTC 
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Comment 4 Gilles Dubreuil 2017-11-16 23:51:43 UTC 
Aforementioned PR#2543 addresses the issue by not using `selectpicker-for-select-tag` at a cost of slightly different look & feel on the FW rules tables until further investigation.
Comment 6 Gilles Dubreuil 2017-11-21 23:50:12 UTC 
PR#2543 merged
Note You need to log in before you can comment on or make changes to this bug.