Bug 1401975 - [RFE] Chargeback should allow users to specify "subscription" prices.
Summary: [RFE] Chargeback should allow users to specify "subscription" prices.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.6.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-06 13:44 UTC by Raul Mahiques
Modified: 2019-07-08 12:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-08 12:08:58 UTC
Category: Feature
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Raul Mahiques 2016-12-06 13:44:56 UTC
Description of problem:
When i create a chargeback report on Rates i cannot set a fixed amount for a period of time:

Customer wants to charge 100 per CPU per year, it doesn't matter if the server runs for 24h or for 1 year, during that period it will be charged 100, if the server still alive the year after, then it will be charged another 100.

So a the end of the period they have chosen if the server was created since the last report and didn't change then it will be charge, if the server was charged for already in the previous report then it won't be charged double.


ie.
Costs: 1 CPU allocation costs 100 per year.
serverX created -- After one hour decommissioned ---> cost 100 (1 cpu at 100)
serverY created -- After 34 days decommissioned ---> cost 100 (1 cpu at 100), report runs every month, server will only appear in the first report, not the second because it's already paid.

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

How reproducible:
Just try to create a report.

Steps to Reproduce:
1.Not relevant

Actual results:
Not possible to specify this type of charge.

Expected results:
as per the description.

Additional info:


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