Story: Sprint 24 quick bug fixes: currency CRUD, party re-provisioning
Table of Contents
This page documents a story in Sprint 24. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Bundle three small, unrelated bugs pulled in from the inbox — each blocking or degrading basic functionality:
- The Qt client's Currency add dialog never enables Save even after all required fields are filled in, blocking currency creation entirely.
- The currencies list window's pagination controls don't work, unlike other entity list windows — large currency lists are unusable/incomplete.
- Re-provisioning a party throws a raw Postgres duplicate-key error instead of skipping/upserting cleanly.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 24 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-07-22 |
Acceptance
- Filling in all required fields in the Currency add dialog enables Save; a new currency can be created from the Qt client.
- The currencies list window pages correctly for a list with more entries than one page.
- Re-running party provisioning against an already-provisioned party succeeds (skip/upsert) instead of throwing a raw duplicate-key error — superseded by the bundle-provisioning story (see Decisions).
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Currency add dialog: Save button stays disabled | DONE | 2026-07-22 | 2026-07-22 | Save button remains disabled even after filling in all required fields when adding a new currency, blocking creation. |
| Currencies list window paging does not seem to work | DONE | 2026-07-22 | 2026-07-22 | The currencies list window's pagination controls don't appear to be enabled/working, unlike other entity list windows. |
| Party re-provisioning fails on duplicate report definitions | ABANDONED | provision party –reports all in ores.shell/Qt wizard throws a raw Postgres duplicate-key error instead of skipping/upserting cleanly when re-run against an already-provisioned party. |
Decisions
- "Party re-provisioning fails on duplicate report definitions" abandoned: superseded by Make party-scoped bundle provisioning data-driven, not one hand-written phase per bundle, which routes report definitions through the already-idempotent =dq.v1.bundles.publish=/publish-from-dq path, retiring the per-record RPC loop that threw the duplicate-key error.