Red Hat Bugzilla – Bug 838457
PRD32 - webadmin: the default of the tree should be expanded with DCs, at least
Last modified: 2013-07-03 22:48:18 EDT
Description of problem:
If you want to use the tree, you have to expand it. You currently have two options:
1. Click 'Expand All'
2. Start to expand the tree, level by level.
We can save at least a click in the 2nd option if we already expand the tree to at least its first level - DC level. I'm not sure if we shouldn't even expand it to the 2nd level as well.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
worth looking at bug 879291 while at it.
Andrew: Any preference to which level we should expand by default [first level (i.e. DCs only)? second level (i.e. DCs + Clusters)]?
Kaul, see question in Comment #2?
I personally prefer the 2nd level, not so much because of the clusters but because of the Storage
posted upstream: http://gerrit.ovirt.org/#/c/10427/
merged at: http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=b2a6031cb1be5ab8e0651f0aca8264d5e3d27c1b
ok, sf5, i can see tree -> dc -> dc's top elements.
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.