Bug 847068 - [RFE] After new VM creation, select this VM in the webadmin
Summary: [RFE] After new VM creation, select this VM in the webadmin
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Yaniv Kaul
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-09 15:08 UTC by David Jaša
Modified: 2016-03-27 06:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 847066
Environment:
Last Closed: 2016-03-27 06:47:55 UTC
oVirt Team: UX
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description David Jaša 2012-08-09 15:08:22 UTC
webadmin is affected as well and consequences may be even more serious.

+++ This bug was initially created as a clone of Bug #847066 +++

Description of problem:
After new VM creation, select this VM. Currently, existing VM selection is preserved, meaning that if a user chooses to do anything in a VM sub-tab, he has to first click the VM. If another VM is selected prior to VM creation, user is likely to modify older VM instead of a newly created one.

This is mainly an ergonomic issue but it may lead to serious errors.

Version-Release number of selected component (if applicable):
si13.2:
rhevm-userportal-3.1.0-11.el6ev.noarch
rhevm-webadmin-portal-3.1.0-11.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1. select a VM "1" in User Portal
2. create v VM "2", hit OK
3.
  
Actual results:
VM "1" keeps being selected

Expected results:
VM "2" is selected (or alternatively no VM is selected but VM "2" is a better choice IMO)

Additional info:
webadmin is affected as well

Comment 1 Itamar Heim 2013-02-10 07:04:32 UTC
einav - thoughts (in webadmin, we have the search consideration as well)

Comment 2 Einav Cohen 2013-02-22 01:29:37 UTC
need to decide if in addition to selecting the newly-created item, the already-selected item(s) remain selected.

if previous selection is retained - probably need to make sure that the newly-created item becomes the "main" selected item (i.e. the sub-tabs are displayed in its context, etc.).

if previous selection is not retained, the newly-created item will become the "main" selected item by definition, since it will be the only selected item.

also: search considerations: if the newly-created item doesn't match the current search-criteria, it won't be displayed in the grid [1].
not sure what is the better/expected behavior in this case: retaining previous selection or not retaining previous selection.


[1] we can also decide that a newly-created item should always be added to the grid, regardless if it matches the current search-criteria or not, but that's a separate discussion / feature.

Comment 3 Itamar Heim 2013-12-01 10:07:13 UTC
thoughts on effort vs. impact?

Comment 4 Einav Cohen 2013-12-11 01:47:04 UTC
taking [1] out of the equation: I don't think that it is hard to implement, and it is sort of a paper-cut from the ux perspective, i.e. it is worth solving. 

however, as with other auto-selection requests that we have, there might be some pitfalls that we are currently not aware of. 

also: taking [1] into consideration might add a considerable amount of work, depending on the exact determined solution. 

[1] from comment #2: if the newly-created item doesn't match the current search-criteria, it won't be displayed in the grid. 
we can also decide that a newly-created item should always be added to the grid, regardless if it matches the current search-criteria or not, but that's a separate discussion / feature.

Comment 5 David Jaša 2013-12-11 09:20:49 UTC
(In reply to Einav Cohen from comment #4)
> ...
> also: taking [1] into consideration might add a considerable amount of work,
> depending on the exact determined solution. 
> 
> [1] from comment #2: if the newly-created item doesn't match the current
> search-criteria, it won't be displayed in the grid. 
> we can also decide that a newly-created item should always be added to the
> grid, regardless if it matches the current search-criteria or not, but
> that's a separate discussion / feature.

If the new item doesn't match current search, simply select nothing. That's IMO better than including in view item that shouldn't be there (when the item should disappear - on its deselection? on main tab change? ...) or keep selected something else that user will edit instead of the new thingy (that happened to me _many_ times - not cool). The flow:
  1) have search
  2) create something
  3) give the new entity a setting that will make it show up in a search
  4) have the search again, now with newly created item
would be IMO better provided by keeping track of search history (display recent searches when keyboard focus is given to search field but nothing is typed).


Note You need to log in before you can comment on or make changes to this bug.