Bug 1434077 - reports do not distinguish between same name custom attributes with different sections
Summary: reports do not distinguish between same name custom attributes with different...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Libor Pichler
QA Contact: Niyaz Akhtar Ansari
URL:
Whiteboard:
Depends On:
Blocks: 1452764 1458341
TreeView+ depends on / blocked
 
Reported: 2017-03-20 16:54 UTC by Ari Zellner
Modified: 2018-03-06 14:56 UTC (History)
7 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1452764 1458341 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:56:12 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ari Zellner 2017-03-20 16:54:13 UTC
Description of problem:
Cant tell between two labels an entity might have in a report.
if the entity has 2 labels, one: {section:'labels 'name: 'test' value:'1'}
and two: {section:'docker_labels 'name: 'test' value:'2'} you cant add one label but not the other to the report or know which one is which


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

How reproducible:
Create a new report based on an entity with 2 types of custom attributes(labels) 
(for example Container Image) and try to add one type of label and not the other

Steps to Reproduce:
1. Cloud Intel -> reports -> create new report
2. Base report on 'Container Image'
3. Have a look at the custom attribute columns in the selectable columns list

Actual results:
Cannot distinguish between labels from different ssections

Expected results:
Have some sort of indicator to which section each label column belongs to

Additional info:

Comment 7 Niyaz Akhtar Ansari 2017-12-14 07:01:15 UTC
Verified in Version 5.9.0.13.20171212214416_f4f190a


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