Bug 1323741

Summary: [RFE] custom attributes do not display correctly in dashboard widget charts
Product: Red Hat CloudForms Management Engine Reporter: Colin Arnott <carnott>
Component: ReportingAssignee: Libor Pichler <lpichler>
Status: CLOSED DUPLICATE QA Contact: Matouš Mojžíš <mmojzis>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5.0CC: benglish, dmisharo, jhardy, jocarter, lpichler, nachandr, obarenbo, yrudman
Target Milestone: GAKeywords: FutureFeature, RFE
Target Release: cfme-future   
Hardware: x86_64   
OS: Linux   
Whiteboard: widget:dashboard:report
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-28 12:46:19 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:

Description Colin Arnott 2016-04-04 15:03:59 UTC
Description of problem:
I would like to create dashbord chart from custom report based on custom evm service attributes. I have attached to my all services custom attribute in format "key" -> "value". Value is the decimal number. I am able to create report from those custom attributes (EVM custom attribute: {Name,Value}), but I am not able to create chart because the attribute (EVM custom attribute: value) is not in the numeric format and there is no possibility to change to formatting.

Version-Release number of selected component (if applicable):
cfme-5.5.2.4-1.el7cf.x86_64

How reproducible:
requires custom attributes in vmdb

Steps to Reproduce:
0. have custom attributes in vmdb
1. create a report that uses custom attributes
2. create a chart widget based on this report
3. add to the dashboard

Actual results:
blank chart widget

Expected results:
chart widget with fully populated custom attribute data

Comment 7 Josh Carter 2019-01-24 19:29:12 UTC
Can we have QE retest this? We believe this is working in the current version

Comment 8 Yuri Rudman 2019-02-28 12:46:19 UTC

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