Bug 36662 - UVMM does not show which value is invalid
UVMM does not show which value is invalid
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Virtual machines (UVMM)
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-13 17:11 CET by Janek Walkenhorst
Modified: 2023-06-28 10:51 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Janek Walkenhorst univentionstaff 2014-11-13 17:11:11 CET
(Observed with Bug #36661)

When an invalid value is entered the module does not show where the value is, if it is on a different page.

Additionally the message only says "the value" is invalid, not which.
Comment 1 Florian Best univentionstaff 2017-07-17 15:35:26 CEST
I don't understand this. Can you give more information, e.g. an example and a screenshot.
Comment 2 Philipp Hahn univentionstaff 2018-10-26 13:45:52 CEST
1. Open UVMM
2. Edit an existing VM
3. Go the "Advanced" tab
4. Change values there to some values not available from the ComboBox dropdown
5. [Go back to "General" tab]
6. Click "save"
7. You get the following error dialog:
  Notification
  The entered data is not valid. Please correct your input.
8. The "Advanced" tab containing illegal values is not flagged with a red exclamation mark as it is done for example in the UDM modules.
Comment 3 Ingo Steuwer univentionstaff 2021-05-14 13:47:58 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.