Task: Extract the ores.reporting user journeys
Table of Contents
This page documents a task in the Extract the user journeys that replace the ores.qt screens story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Every journey a person had in ores.reporting is documented as a user journey, and every action its legacy Qt screens offered is covered by a journey or recorded as dropped. Order 8 of 13.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent story | Extract the user journeys that replace the ores.qt screens |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Begin implementation. |
| Last touched | 2026-09-23 |
3. Acceptance
- Every item of the User Journey Extraction Standard passes, with its evidence recorded below.
- Every Qt action has a disposition: kept, changed or dropped.
- Every defect found is captured, and every recurring gap is recorded.
4. Plan
Work the User Journey Extraction Standard in its section order and record each item below.
- Inventory (I01 to I05).
- Legacy Qt screens (Q01 to Q05).
- Vocabulary and screen rules (V01 to V03).
- Journeys (J01 to J08), ending with the catalogue agreed.
- Documents (D01 to D05).
- Verification and gaps (X01 to X05).
| Item | Result | Evidence |
|---|---|---|
5. Notes
- Legacy screens:
ores.qt/reportingat/home/marco/Development/OreStudio/ores.qt, orgit show af67db3062^:projects/ores.qt/.... Survey on 2026-09-23: 4.uifiles and 12 headers declaring a window, dialog, wizard, widget, view, panel or page. - Starts after Clean ores.reporting to the component clean standard, because the coverage tables check against the generated protocol.
6. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
7. PRs
| PR | Title |
|---|---|
8. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|