Bug 1465960 - [New UI] - Add green colors to the Link up and plugged icons in the VM nic panel and red color for link down state
Summary: [New UI] - Add green colors to the Link up and plugged icons in the VM nic pa...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ovirt-4.2.0
: ---
Assignee: Greg Sheremeta
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-28 14:12 UTC by Michael Burman
Modified: 2017-06-29 16:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-29 16:41:31 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshots (3.36 KB, application/x-gzip)
2017-06-28 14:18 UTC, Michael Burman
no flags Details

Description Michael Burman 2017-06-28 14:12:19 UTC
Description of problem:
[New UI] - Add green colors to the Link up and plugged icons in the VM nic panel.

There should be indication of the up state and plugged state with green color for the VM's nic panel(just like we have in the edit nic dialog).
It should be clearly visible that the nic is up and plugged.

- Also we should add red color for the link down state(we have for unplugged) as it currently show arrow down icon with gray color. It's hard to understand that the link is down.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170627181935.git9424f9b.el7.centos

Comment 1 Michael Burman 2017-06-28 14:18:43 UTC
Created attachment 1292660 [details]
screenshots

Comment 4 Greg Sheremeta 2017-06-29 16:41:31 UTC
grayscale by design (PatternFly standard). UI is moving to using colored icons only when there is an alerting type situation.

We are planning an icon overhaul for 4.2, and I'll remember to give the design team your feedback that it's currently hard to differentiate.


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