User Story

As a user I want a to expand my options when creating a cost model so that the cost reported better fits my needs.  I would like to expand in the following way:

1. Allow multiple rates for the same metric, measurement, and calculation type
2. Allow setting rates on a specific tag or group of tags (based on tag key) for a particular metric, measurement, and calculation type combination.

Prioritization / Business Case

• This feature let's users more dynamically assign cost to OpenShift clusters.

Impacts

• API
• Data Backend
• UI
• UX

UX Requirements

• COST-25 addresses the UX work for #1 & #2 requirements

UI Requirements

• COST-79 addresses the UI work for #2 requirements
• COST-19 addresses the UI work for #1 requirements (as a sub-task: COST-271)

Documentation Requirements

• What documentation is required to complete this epic?

Backend Requirements

• Are there any prerequisites required before working this epic?

QE Requirements

• Does QE need specific data or tooling to successfully test this epic?

Release Criteria

• Can this epic be released as individual issues/tasks are completed?
• Can the backend be released without the frontend?
• Has QE approved this epic?