Bug 1182569
| Summary: | [RFE] Iso domain's attach button should be greyed out with a tooltip when domain is already attached to all available dc's on system | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Ori Gofen <ogofen> | ||||
| Component: | Frontend.WebAdmin | Assignee: | Nobody <nobody> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Raz Tamir <ratamir> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5.0 | CC: | acanan, amureini, bugs, gklein, lsurette, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi | ||||
| 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: | Environment: | ||||||
| Last Closed: | 2017-03-13 11:41:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 910354 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Einav - does this make sense from a UX perspective (i.e., does it "fit" the rest of the application)? (In reply to Allon Mureinik from comment #1) > Einav - does this make sense from a UX perspective (i.e., does it "fit" the > rest of the application)? yes and no :) this may make sense from a UX perspective, but it is not in line with the rest of the UI. we are graying-out buttons only when it is "dead-obvious" to do so (e.g. we will gray out the 'run' button for an 'Up' VM), but if the user will potentially have a hard time understanding why the button is grayed out, we will not do so and block the user from performing the action only when in the dialog context. a probably better solution from a UX perspective is to gray-out the button and provide a tool-tipped reason when hovering on it, but it requires an infrastructure which, AFAIK, we don't have / we lost sometime ago (see bug 910354). so as for this BZ: I recommend closing it, or turning it to an 'Improvement' BZ that depends on bug 910354. thanks. Thanks Einav! Marking this bug as dependent on bug 910354, and we'll see when (if?) we can handle it. (In reply to Allon Mureinik from comment #3) > Thanks Einav! > > Marking this bug as dependent on bug 910354, and we'll see when (if?) we can > handle it. Resetting target version, as bug 910354 is not targeted yet. We'd like to deprecate the ISO domain and this is a low priority RFE - closing for the time being. |
Created attachment 980498 [details] pic Description of problem: see picture Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: