this is seemingly a simple change, however I am afraid of potential pitfalls here, so we need to make sure that we will well-define the correct behavior. the main pitfalls that I can think of are: - what should happen if the selected item disappears from the grid (since it has been removed, or since the user changed the search string, etc.)? should the first item in the updated grid be selected automatically? or should the grid remain without a selected item? - "tomorrow" we will add an option to auto-select a newly-added item (see bug 847066), which might not be the first item in the grid. if we will have something already selected, it might look weird that the selection will change all of a sudden once the newly-created item will be displayed in the grid. it can happen today as well, but today I assume that in a lot of the cases, the "New" dialog is being opened without anything selected in the grid before that; in this case, selecting the newly-created item once it appears makes sense. however, if we will address this BZ - we will *always* have something selected before creating the new item, so the somewhat-weird/unexpected behavior of selection change will always occur. - when explicitly de-selecting an item, leaving the grid without any selected items: I assume we want to keep it that way, and not automatically select the first item in the grid afterwards? @Malini/Eldan - any additional thoughts / comments on the above?
Kevin: we are thinking about auto-selecting an item once logging into the application (in the VMs main tab that is selected by default), and upon changing the selected tab; will that be sufficient?
*** Bug 958309 has been marked as a duplicate of this bug. ***
If the selection comes from the tree and you select an Item - yes it's logic. We are even planning to make later on a splash screen to each entity selected from the tree and not to show only 1 line in a grid.
*** Bug 962663 has been marked as a duplicate of this bug. ***
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. https://rhn.redhat.com/errata/RHSA-2015-0158.html