Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1116847

Summary: [RFE] Enhance work (sub-tab) flows when working in tree (filtered) mode
Product: [Retired] oVirt Reporter: Gilad Chaplik <gchaplik>
Component: ovirt-engine-webadminAssignee: bugs <bugs>
Status: CLOSED WONTFIX QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5CC: dfediuck, ecohen, gklein, iheim, mgoldboi, rbalakri, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ux
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-11 20:27:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
example none

Description Gilad Chaplik 2014-07-07 13:06:11 UTC
Created attachment 916076 [details]
example

Description of problem:
When working with the tree view (left hand side tree pane), there are situations where data in subtabs is trivial, causing users additional unneeded flows, and imo results in users not using the tree, and benefit visualization of data.

How reproducible:
100%

Steps to Reproduce (Example- see attachment):
1. select specific DC in the tree
2. goto storage -> DC subtab
3. select DC and maintenance Storage.

Actual results:
There is only a single DC (trivial).

Expected results:
The actions Attach, Detach, Activate, Maintenance should be pulled up to main tab level, and there's no reason to select DC sub-tab (although it can be presented for additional info).

Additional info:
The fix should introduce an infra for the above, including mapping all possibilities in tree/tabs, and suggest a good UX for pull-up actions.

Comment 1 Itamar Heim 2015-04-11 20:27:27 UTC
I don't see us fixing this not as part of a 4.0 re-haul

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.