← Back to parent Epic
MAZENG-FT-34 · Understand deployment distribution
Why it matters
A user needs to see where recorded deployments run and how they are distributed across lifecycle stages.
Expected outcome
Stage and geographic views make the recorded deployment footprint understandable without presenting synthetic data as fact.
In scope
- Group non-archived deployment counts by configured project stage.
- Map recognized provider regions geographically.
- Show explicit unknown and empty states for missing stage or location data.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Deployment counts are grouped by configured project stage.
- 02
Deployment regions are presented geographically using recognized provider-region mappings.
- 03
Archived projects and resources are excluded.
- 04
Missing stage and location data produce explicit empty/unknown states rather than misleading data.
Dependencies and risks
Dependencies
None recorded.
Risks
- Reporting depends on valid project tags and a maintained region-to-country map.
- Legacy stage reporting substitutes fixture defaults when no records exist.
- Legacy location reporting inserts synthetic Fiji data solely to render an empty map; that defect must not be retained.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.