Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1396174 [details] Screenshot from editing a report menu Description of problem: Unable to add a report to a Report Menu for a group. The "Available Reports" section is not populated with any report. Version-Release number of selected component (if applicable): 5.8.2.3 How reproducible: Always Steps to Reproduce: 1. Navigate to Cloud Intel -> Reports / Edit Report Menus 2. Select a group to edit the report menus of 3. Select a folder to add a report to Actual results: The "Available Reports" area is blank Expected results: Unselected reports are listed in the "Available Reports" area and are able to be moved to the "Selected Reports" area. Additional info:
https://github.com/ManageIQ/manageiq-ui-classic/pull/3412
New commit detected on ManageIQ/manageiq-ui-classic/fine: https://github.com/ManageIQ/manageiq-ui-classic/commit/4b0a8958962648de539c976d926e99d38f0cfb73 commit 4b0a8958962648de539c976d926e99d38f0cfb73 Author: Harpreet Kataria <hkataria> AuthorDate: Thu Feb 15 15:05:59 2018 -0500 Commit: Harpreet Kataria <hkataria> CommitDate: Thu Feb 15 15:05:59 2018 -0500 Show custom reports in menu editor as available reports. Fixed code to show Custom reports in Available Reports box in menu editor. Code has been refactored and fixed on Upstream and G release, this is a Fine specific fix. Fixed existing spec test backported fixes from https://github.com/ManageIQ/manageiq-ui-classic/pull/3245 to Fine Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1496924 https://bugzilla.redhat.com/show_bug.cgi?id=1545441 app/controllers/application_controller.rb | 112 +- app/controllers/report_controller/menus.rb | 6 +- app/controllers/report_controller/schedules.rb | 2 +- spec/controllers/miq_report_controller/menus_spec.rb | 14 +- spec/controllers/miq_report_controller/trees_spec.rb | 2 +- spec/controllers/report_controller_spec.rb | 52 +- 6 files changed, 79 insertions(+), 109 deletions(-)
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-2018:1109