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

Bug 1094021

Summary: [RFE] make disabled form field reasons more intuitive
Product: [oVirt] ovirt-engine Reporter: Ilanit Stein <istein>
Component: Frontend.WebAdminAssignee: Nobody <nobody>
Status: CLOSED DEFERRED QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: bugs, gshereme, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ---Keywords: FutureFeature, Improvement, UserExperience
Target Release: ---Flags: oourfali: 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: 2020-04-01 14:44:42 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:
Attachments:
Description Flags
Example screen shot
none
still needs work in 4.2 none

Description Ilanit Stein 2014-05-04 12:29:02 UTC
Description of problem:

Using the help info, that pop ups is problematic for the following reasons:

1. Not intuitive: User is not aware of it's existence. 
I myself discovered it by chance, following standing with the mouse on greyed out field for several sec.
2. Not consistent: Not implemented for ALL such cases.
3. It is seen only if drugging the mouse from out side of the field, into the field. That is if entered with the mouse to the field, and move inside of it, the help message will not be displayed.

Therefore, please move the help info to be under the "tool tip" help, visible to user with the question mark, near the relevant field in UI.

Version-Release number of selected component (if applicable):
av8.1

Example:
See attached screen shot of cpu pinning.

Comment 1 Ilanit Stein 2014-05-04 12:29:44 UTC
Created attachment 892280 [details]
Example screen shot

Comment 2 Einav Cohen 2014-05-20 17:11:14 UTC
we may need to consider a overhaul of this as part of the GUI overhaul for 4.0.

Comment 3 Yaniv Kaul 2015-11-16 16:09:46 UTC
Marking to be considered for 4.0

Comment 4 Greg Sheremeta 2017-11-30 22:19:08 UTC
Still needs work as of 4.2. See screenshot.

Comment 5 Greg Sheremeta 2017-11-30 22:19:38 UTC
Created attachment 1361321 [details]
still needs work in 4.2

Comment 6 Michal Skrivanek 2020-03-18 15:43:50 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 7 Michal Skrivanek 2020-03-18 15:47:02 UTC
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 8 Michal Skrivanek 2020-04-01 14:44:42 UTC
ok, closing. Please reopen if still relevant/you want to work on it.

Comment 9 Michal Skrivanek 2020-04-01 14:49:36 UTC
ok, closing. Please reopen if still relevant/you want to work on it.