Story: Design and seed the reports, configurations and portfolio trees each ACME party runs
Table of Contents
This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Each ACME party gets the reports it would really run, with the configuration those reports need and a realistic portfolio tree, root portfolio and currencies.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 30 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-11-08 |
3. Acceptance
- A design document states, for each of the four parties, which reports it runs and why, from its role, its jurisdiction and its place in the group, with the alternative rejected.
- Provisioning gives each party only the reports in the design, and each party's report definitions carry the configuration they need with a base currency that matches the party.
- Each party has a realistic portfolio tree, root portfolio and currencies, and each report scope names portfolios that exist for that party.
- The seeds the task touches carry no comment that states a count, and the task records what a clean provision did not prove.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Design the reports, configs and portfolio trees each ACME party runs | DONE | 2026-10-11 | 2026-11-08 | Give each ACME party the reports it would really run, with the configuration those reports need and a realistic portfolio tree, root portfolio and currencies. Record and justify every decision for later review. |
5. Decisions
- PRs #3128 and #3136 delivered the design and the seeds. (review at sprint 30 start, 2026-11-08.)