Is the 'Move' action a more frequent action than Activate and Deactivate? If yes, then, it may make sense to move it so it precedes the 'Activate' action. This way it is consistent with the way the actions display on the main 'Disks' tab (where the activate/ Deactivate are not present though). I think even more than moving this button/ action though, the solution to this problem is in grouping actions and separating them with separator lines. Possibly even more important is to have a confirmation dialog when the user clicks on remove or deactivate. If this confirmation dialog existed, I suspect the position would not be the bigger issue.
Ayal provided me these comments offline - Q: Is the 'Move' action a more frequent action than Activate and Deactivate? If yes, then, it may make sense to move it so it precedes the 'Activate' action. This way it is consistent with the way the actions display on the main 'Disks' tab (where the activate/ Deactivate are not present though). A: I cannot say, depends on the use case, but in general there isn't really any reason to deactivate disks (and hence activate later on). Moving should be very low frequency as well. note that deactivate and activate are quite fast (order of seconds) while move can be in the order of hours. Q: I think even more than moving this button/ action though, the solution to this problem is in grouping actions and separating them with separator lines. Possibly even more important is to have a confirmation dialog when the user clicks on remove or deactivate. If this confirmation dialog existed, I suspect the position would not be the bigger issue. A: +1 Warning before move should definitely be there. Actually same should be for deactivate. I also like the grouping as long as it's visually easy on the eye.
Based on the input above, I think the recommendation to resolve this bug from a UX perspective is to add a confirmation message for both deactivate and Move. We will not change the positions of the actions yet but we should look into adding separators in our toolbars to define some groupings of actions. I will open a RFE for that.
(In reply to mrao from comment #3) > ... we should look into adding separators in our toolbars to define some > groupings of actions. I will open a RFE for that. opened: bug 1045573 (ovirt, ux)
This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA
verified using 3.4 av2 TCMS run - https://tcms.engineering.redhat.com/run/119313/
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. http://rhn.redhat.com/errata/RHSA-2014-0506.html