Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688871 - Unable to see dialog details passed to catalog after upgrade from 5.9.4 to 5.9.6
Summary: Unable to see dialog details passed to catalog after upgrade from 5.9.4 to 5.9.6
Keywords:
Status: POST
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.9.z
Assignee: eclarizi
QA Contact: Jaroslav Henner
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1670327
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-14 15:52 UTC by Satoe Imaishi
Modified: 2019-04-12 03:13 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1670327
Environment:
Last Closed:
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:


Attachments (Terms of Use)

Comment 2 CFME Bot 2019-03-14 16:01:16 UTC
New commit detected on ManageIQ/manageiq/gaprindashvili:

https://github.com/ManageIQ/manageiq/commit/2d74dddac305d03fdf72bbb50d73ef98ba5dde2e
commit 2d74dddac305d03fdf72bbb50d73ef98ba5dde2e
Author:     Joe Rafaniello <jrafanie@users.noreply.github.com>
AuthorDate: Fri Mar  8 11:49:07 2019 -0500
Commit:     Joe Rafaniello <jrafanie@users.noreply.github.com>
CommitDate: Fri Mar  8 11:49:07 2019 -0500

    Merge pull request #18469 from eclarizio/BZ1670327

    Fix for inability to see dialog details passed to catalog after upgrade from 5.9.4 to 5.9.6

    (cherry picked from commit 16dabe5eb0b833ca8fbec7bb9ac34ed937be4189)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1688871

 app/models/dialog.rb | 2 +
 spec/models/dialog_spec.rb | 40 +-
 2 files changed, 32 insertions(+), 10 deletions(-)


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