Story: Extract the remaining component user journeys
Table of Contents
This page documents a story in Product backlog — inbox. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
Every component left after the extraction standard and the ores.refdata pass has its user journeys documented under the User Journey Extraction Standard, and every action its legacy Qt screens offered is covered by a journey or recorded as dropped: analytics, the application shell, compute, dq, iam, marketdata, reporting, scheduler, synthetic, trading, workflow and workspace.
This story was split from Extract the user journeys that replace the ores.qt screens when that story was reworded to the standard and the ores.refdata journeys it delivered and closed DONE at the sprint 26 close on 2026-10-05; its thirteen remaining component tasks moved here.
2. Status
| Field | Value |
|---|---|
| State | STARTED |
| Parent sprint | Sprint 26 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Extract the component journeys in order, starting with the application shell. |
| Last touched | 2026-10-05 |
3. Acceptance
- Every component task below is DONE: its journeys are documented under the standard, its Qt actions all have a disposition, and its defects and gaps are recorded.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Extract the ores.analytics user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.analytics, reading its legacy screens in ores.qt/analytics. | ||
| Extract the application shell user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.qt application shell, reading its legacy screens in ores.qt/application. | ||
| Extract the ores.compute user journeys | STARTED | Run the User Journey Extraction Standard for ores.compute, reading its legacy screens in ores.qt/compute. | ||
| Extract the ores.dq user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.dq, reading its legacy screens in ores.qt/dq. | ||
| Extract the ores.iam user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.iam, reading its legacy screens in ores.qt/iam. | ||
| Extract the ores.marketdata user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.marketdata, reading its legacy screens in ores.qt/marketdata, ores.qt/mktdata. | ||
| Write the refdata party, book, convention and tenor journeys | BACKLOG | Write journeys 5 to 9 of the agreed ores.refdata catalogue: counterparty onboarding, party details, book structure, instrument conventions and tenor resolution. | ||
| Extract the ores.reporting user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.reporting, reading its legacy screens in ores.qt/reporting. | ||
| Extract the ores.scheduler user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.scheduler, reading its legacy screens in ores.qt/scheduler. | ||
| Extract the ores.synthetic user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.synthetic, reading its legacy screens in ores.qt/synthetic. | ||
| Extract the ores.trading user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.trading, reading its legacy screens in ores.qt/trading. | ||
| Extract the ores.workflow user journeys | BACKLOG | Run the User Journey Extraction Standard for ores.workflow, reading its legacy screens in ores.qt/workflow. | ||
| Extract the ores.workspace user journeys | ABANDONED | 2026-10-05 | Run the User Journey Extraction Standard for ores.workspace, reading its legacy screens in ores.qt/workspace. | |
| Prototype the compute journeys | DONE | 2026-10-07 | Write the compute journeys and walk them as a clickable prototype, so the grid's screens are designed against the activities a person performs rather than against the legacy Qt client. |