Bug 995577 - [RFE] Entities like Roles, policies and properties should have clearly readable names with spaces
Summary: [RFE] Entities like Roles, policies and properties should have clearly readab...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Pavel Stehlik
URL:
Whiteboard: ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-09 18:46 UTC by mrao
Modified: 2015-11-11 14:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-11 14:02:56 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:
sherold: Triaged+


Attachments (Terms of Use)

Description mrao 2013-08-09 18:46:14 UTC
Description of problem: Currently, all filters, load balancing criteria and parameters in the Configure> Cluster policy details dialog appear without any spaces between words ( e.g CpuOvercommitDurationMins) or UserVmManager (in Configure> Roles). While the underlying reasons are understood, it seems like the UI is exposing stuff from under the hood and the end result looks less than polished and affects readability. The expectation that spaces should not exist in the REST-API is strong but that it should exist in the UI is basic. Therefore inconsistency is not an issue. 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results: In the UI, spaces should display even if it means there is some transformation that happens between the records retrieved from the database and what gets displayed on the screen.


Additional info:

Comment 1 Itamar Heim 2014-01-26 08:15:35 UTC
einav - thoughts? scope?

Comment 2 Einav Cohen 2014-01-27 19:42:46 UTC
(In reply to Itamar Heim from comment #1)
> einav - thoughts? scope?

probably requires a lot of work compared to what we will eventually gain. Unfortunately I don't see us getting there any time soon.


Note You need to log in before you can comment on or make changes to this bug.