You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Brian Federle (JIRA)" <ji...@apache.org> on 2014/03/21 21:33:43 UTC

[jira] [Resolved] (CLOUDSTACK-6272) UI > Instance > actions > make it easy to distinguish between the action that fires recoverVirtualMachine API and the action that fires restoreVirtualMachine API

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Federle resolved CLOUDSTACK-6272.
---------------------------------------

    Resolution: Fixed

> UI > Instance > actions > make it easy to distinguish between the action that fires recoverVirtualMachine API and the action that fires restoreVirtualMachine API
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6272
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6272
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>            Reporter: Jessica Wang
>            Assignee: Brian Federle
>             Fix For: 4.4.0
>
>
> (1) Label the action icon that fires recoverVirtualMachine API as "Recover". 
>     Label the action icon that fires restoreVirtualMachine API as "Reinstall". 
> (2) change text in confirmation dialog of Reinstall action as: 
> e.g. "The VM will be reinstalled from template, all current data will be lost, proceed with caution! Extra data volumes, if any, will not be touched."
> (3) Change Reinstall icon to use a 'recycle' symbol, to avoid confusion w/ reboot VM



--
This message was sent by Atlassian JIRA
(v6.2#6252)