Bug 995755

Summary: webadmin [Tree]: should inform user why name cannot be edited in tree context
Product: [Retired] oVirt Reporter: Greg Sheremeta <gshereme>
Component: ovirt-engine-webadminAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, iheim, mgoldboi, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-10 21:30:17 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:

Description Greg Sheremeta 2013-08-10 21:07:48 UTC
Description of problem:
When a specific item is selected in the left-pane tree, and a user tries to edit that item, the name is disabled for editing because the item is currently selected. This is the correct behavior. However, there should also be a message printed to the user that explains *why* the name cannot be edited.

There is code in the application to show a message, but it is not working.

Example:
In HostListModel.java
innerHostModel.getName().setInfo("Cannot edit Host's Name in this tree context"); //$NON-NLS-1$

At current count there are about 20 of these in uicommonweb. I don't see any evidence that the application uses these messages.

How reproducible:
Always

Steps to Reproduce:
1. Select an actual host in the tree.
2. Click edit.
3. You cannot edit the host name. There is no help to tell you why.

Actual results:
There is no help to tell you why you cannot edit the name.

Expected results:
There should be a message shown that says something like "Cannot edit Host's Name in this tree context"

Comment 1 Einav Cohen 2013-08-10 21:30:17 UTC
setInfo is deprecated. it should be replaced with a call to "setChangeProhibitionReason". this will be taken care of in the context of bug 995754 -> marking as duplicate.

*** This bug has been marked as a duplicate of bug 995754 ***