Red Hat Bugzilla – Bug 1330580
Widgets drag and drop is broken in Reports
Last modified: 2016-06-29 11:54:55 EDT
Description of problem: Unable to rearrange widgets in Reports. Version-Release number of selected component (if applicable): 5.6.0.4-beta2.3.20160421172650_719e256 How reproducible: Always Steps to Reproduce: 1. Navigate to Cloud Intel->Reports 2. Expand Dashboards accordion 3. Got to All Dashboards->Default Dashboard 4. Configuration->Edit this Dashboard 5. Try to rearrange widgets Actual results: Unable to rearrange widgets. Expected results: Drag&drop has to work with widgets.
https://github.com/ManageIQ/manageiq/pull/8292
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/3dd7844f59bd4238fc5f348d946c63289d71dd00 commit 3dd7844f59bd4238fc5f348d946c63289d71dd00 Author: Milan Zazrivec <mzazrivec@redhat.com> AuthorDate: Wed Apr 27 17:27:41 2016 +0200 Commit: Milan Zazrivec <mzazrivec@redhat.com> CommitDate: Wed Apr 27 17:27:41 2016 +0200 Bind sortable properties to sortable-handle class We should not be binding the sortable properties to general elements, such as h2, we should rather have our own class to bind the properties to. This is to avoid situations, where drag & drop functionality in our UI will stop working whenever we change h2 to h3 or vice versa. https://bugzilla.redhat.com/show_bug.cgi?id=1330580 app/assets/javascripts/miq_application.js | 6 +++--- app/views/dashboard/_widget.html.haml | 2 +- app/views/miq_ae_customization/_dialog_resource.html.haml | 2 +- app/views/report/_db_widget.html.haml | 2 +- app/views/report/_widget_form_menu.html.haml | 4 ++-- 5 files changed, 8 insertions(+), 8 deletions(-)
Verified fixed in 5.6.0.5-beta2.4.20160503153816_1fb554f.
https://github.com/ManageIQ/manageiq/pull/8473
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-2016:1348