Description of problem: When using right mouse button for context menu on some table element e.g. one particular VM, there used to be menu with options to start|stop|run once...., now it's not there and only general browser context menu is present. This is true for all items, hosts, clusters, storages.... Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.0.master.20170719072402.gitca6b518.el7.centos.noarch How reproducible: always Steps to Reproduce: 1. open VMs tab 2. open context menu for particular VM 3. Actual results: only general context menu appears Expected results: context menu with items relevant for RHV appears Additional info:
We are pending decision on whether to support that, as it is not aligned with UXD guidelines.
After discussion with PM, we've decided to keep the custom context menu removed for now. We can revisit in the future if we see many user complaints.
(In reply to Greg Sheremeta from comment #2) > After discussion with PM, we've decided to keep the custom context menu > removed for now. We can revisit in the future if we see many user complaints. After discussion on the ovirt users list, and consulting with the PatternFly team, we've decided it makes sense to re-add the context menu.
Note that the right click added will contain the buttons that are at the upper panel, as those are expected to be the ones used mostly. It will only contain single buttons (not menus), as currently there is no representation of sub menus on right click in bootstrap. It will not contain the buttons that appear when you press the three dots. If one of these buttons is widely used, it should move to the action panel (requires code change), and then it will also be automatically added to the context menu (no code change needed).
Verified on ovirt-engine-4.2.0-0.0.master.20171113223918.git25568c3.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.