Bug 847068
Summary: | [RFE] After new VM creation, select this VM in the webadmin | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | David Jaša <djasa> |
Component: | Frontend.WebAdmin | Assignee: | Yaniv Kaul <ykaul> |
Status: | CLOSED WONTFIX | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | --- | CC: | bsettle, bugs, iheim, rbalakri, Rhev-m-bugs, ykaul |
Target Milestone: | --- | Keywords: | FutureFeature, Improvement |
Target Release: | --- | Flags: | ylavi:
ovirt-future?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | 847066 | Environment: | |
Last Closed: | 2016-03-27 06:47:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Jaša
2012-08-09 15:08:22 UTC
einav - thoughts (in webadmin, we have the search consideration as well) 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. thoughts on effort vs. impact? 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. (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). |