Bug 1376519 - Tag Control fields not working in Self-Service UI
Summary: Tag Control fields not working in Self-Service UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: GA
: 5.6.3
Assignee: David Taylor
QA Contact: Shveta
URL:
Whiteboard: ssui
Depends On: 1371291
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 16:05 UTC by Satoe Imaishi
Modified: 2022-07-09 07:58 UTC (History)
14 users (show)

Fixed In Version: 5.6.3.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1371291
Environment:
Last Closed: 2016-11-30 19:53:45 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2839 0 normal SHIPPED_LIVE Important: CFME 5.6.3 security, bug fix, and enhancement update 2016-12-01 00:51:49 UTC

Comment 3 Chris Kacerguis 2016-10-27 14:02:38 UTC
GitHub PR here: https://github.com/ManageIQ/manageiq-ui-service/pull/295

Comment 4 Chris Kacerguis 2016-10-27 14:08:15 UTC
Merged https://github.com/ManageIQ/manageiq-ui-service/pull/295 into master, waiting for Oleg B to backport to Darga and Euwe.

Comment 5 Chris Kacerguis 2016-10-31 13:57:57 UTC
Waiting for merge.

Comment 6 Chris Kacerguis 2016-11-04 00:36:03 UTC
Backported to Darga and Euwe

Comment 7 Niyaz Akhtar Ansari 2016-11-14 10:55:24 UTC
Tag Control fields working fine in Self-Service UI

Verified in Version 5.6.3.0.20161108115816_66df924

Comment 9 errata-xmlrpc 2016-11-30 19:53: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.

https://rhn.redhat.com/errata/RHSA-2016-2839.html


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