Bug 1028471

Summary: merge "Migrate" and "Cancel Migration" buttons
Product: [oVirt] ovirt-engine Reporter: David Jaša <djasa>
Component: Frontend.WebAdminAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: low Docs Contact:
Priority: low    
Version: ---CC: bugs, michal.skrivanek, plightfoot, rbalakri, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-10 10:11:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Jaša 2013-11-08 14:22:24 UTC 
Description of problem:
since "Migrate" makes only sense when "Cancel Migration" is redundant and vice versa, these button could be merged to a single button with label changing based on VM(s) state in order to save space.
When multiple VMs are selected, current logic may be maintained: if all selected VMs are migrate-able (up and not pinned and not in-migration), "Migrate" button is available, if not, the button is disabled.

Version-Release number of selected component (if applicable):
3.3

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Michal Skrivanek 2014-02-28 09:53:01 UTC 
Malini, what do you think about dynamically changing the button/action?

I can think of in multiple selection case is that if I trigger a mass migration and then some of them fail but most of them are migrating…and I still have the highlighted selection - I would like to be able to cancel the remaining ongoing migrations by a single click.
Other than that functionally it's ok, I think.
Comment 2 Omer Frenkel 2015-08-26 14:01:14 UTC 
moving the UX question to Einav
Comment 3 Einav Cohen 2015-08-26 15:39:57 UTC 
(In reply to Michal Skrivanek from comment #1)
> Malini, what do you think about dynamically changing the button/action?
> 
> I can think of in multiple selection case is that if I trigger a mass
> migration and then some of them fail but most of them are migrating…and I
> still have the highlighted selection - I would like to be able to cancel the
> remaining ongoing migrations by a single click.

... or re-trigger the migration for the ones that failed. 
So I think that the scenario of multi-selection (in which you have both migrating and non-migrating VMs) in which we cannot guess what the user would want to do, is a good enough reason for keeping both of the 'Migrate' and 'Cancel Migration' buttons in place.
Comment 4 Red Hat Bugzilla Rules Engine 2015-11-30 20:43:04 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.