Skip to main content

← Back to parent Epic

MAZENG-FT-32 · Review portfolio cost totals and cost history

Feature intent

A user needs to understand the estimated spend represented by all projects they can access and how that estimate changes over time.

Why it matters

A user needs to understand the estimated spend represented by all projects they can access and how that estimate changes over time.

Expected outcome

Portfolio-level totals, periods, currency context, and retained history make estimated cloud spend understandable across projects.

In scope

  • Aggregate the latest retained estimate for each accessible project.
  • Present hourly through annualized totals with explicit currency-conversion state.
  • Chart cost changes from retained project history.
Delivery status
IN_BACKLOG
Owner
RootAtSkic
Parent Epic
MAZENG-EP-9
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    The portfolio total uses the latest retained estimate for every accessible project.

  2. 02

    The user can view hourly, daily, weekly, monthly, and annualized totals.

  3. 03

    Currency conversion clearly identifies the source currency, rate, and refresh/failure state.

  4. 04

    A cost-over-time view uses actual retained history rather than placeholder data.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Projects without a retained estimate may be omitted from portfolio totals.
  • Legacy currency conversion runs directly in the browser against an external service.
  • The legacy cost-over-time endpoint is a stub and zero-valued records can be incorrectly ignored.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source