Bug 1369442 - [RFE] Chargeback Report for containers does not show which rate was used in calculations
Summary: [RFE] Chargeback Report for containers does not show which rate was used in c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: Ari Zellner
QA Contact: Einat Pacifici
URL:
Whiteboard: container:chargeback
Depends On:
Blocks: 1383443
TreeView+ depends on / blocked
 
Reported: 2016-08-23 12:44 UTC by Einat Pacifici
Modified: 2017-06-12 17:09 UTC (History)
6 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1383443 (view as bug list)
Environment:
Last Closed: 2017-06-12 17:09:58 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Chargeback Report screenshot (150.69 KB, image/png)
2016-08-23 12:44 UTC, Einat Pacifici
no flags Details

Description Einat Pacifici 2016-08-23 12:44:41 UTC
Created attachment 1193307 [details]
Chargeback Report screenshot

Description of problem:
When viewing a generated container project chargeback report, there is no indication of the Rate that was used/applied to perform the necessary calculations. 

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

How reproducible:
Always


Steps to Reproduce:
1.Generate a rate for chargeback for containers providers and assign it to a provider
2.Generate a report for the projects of the provider
3.View generated report

Actual results:
Report is generated successfully. However, there is no way of knowing which rates were used to calculate the values shown. 

Expected results:
Some link/indication of the rate that was used and assigned to the containers provider. 

Additional info:
Screenshot attached.

Comment 5 Ari Zellner 2016-09-26 18:07:45 UTC
https://github.com/ManageIQ/manageiq/pull/11523


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