Bug 1524960 - UI inconsistency - Size Unit title missing when adding a new disk
Summary: UI inconsistency - Size Unit title missing when adding a new disk
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.0
Assignee: lgalis
QA Contact: Nandini Chandra
URL:
Whiteboard:
Depends On:
Blocks: 1558144
TreeView+ depends on / blocked
 
Reported: 2017-12-12 11:17 UTC by Jan Zmeskal
Modified: 2019-02-11 14:08 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1558144 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:08:37 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
web element (266.54 KB, image/png)
2017-12-12 11:17 UTC, Jan Zmeskal
no flags Details

Description Jan Zmeskal 2017-12-12 11:17:22 UTC
Created attachment 1366553 [details]
web element

Description of problem:
When adding a new disk to VM, all the different column have their name displayed in the table - only Unit Size has blank field.
Why the name should be there?
1. Consistency
2. It would greatly help automated testing, if the field could be reference by its name. As of now, the table header has no name (see "web element" screenshot). Therefore it must be referenced by it's index in table. That is going to break the automated testing as soon as a column is added or removed.

Version-Release number of selected component (if applicable):
CFME 5.9.0.11
RHV 4.1.7.6

How reproducible:
100 %

Steps to Reproduce:
1. Have RHV provider with powered-off VM
2. Find the VM in CFME, go to its summary page and click Configuration -> Reconfigure this VM
3. See the Disks table

Actual results:
Table column with size unit is missing name

Expected results:
It should be named

Comment 4 Nandini Chandra 2018-11-15 22:42:29 UTC
Verified in 5.10.0.23


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