[Feature] Clarify campaign review workflow steps and possible interventions #63

Closed
opened 2026-07-14 20:08:40 +02:00 by zemion · 2 comments
Owner

Problem / User Need

The campaign build/review workflow needs to make its steps, status, and possible user interventions clearer. Users should understand what each step checks, what problems mean, and what actions are available.

Acceptance Criteria

  • Review steps have clear labels, descriptions, and status outcomes.
  • Each warning/error explains the available intervention path.
  • Users can distinguish critical blockers from non-critical review items.
  • The workflow communicates what has already been reviewed and what still needs attention.

Notes / Decisions

This is partly UX copy and partly workflow-state design. It should align with the broader workflow/guided UI direction.

## Problem / User Need The campaign build/review workflow needs to make its steps, status, and possible user interventions clearer. Users should understand what each step checks, what problems mean, and what actions are available. ## Acceptance Criteria - Review steps have clear labels, descriptions, and status outcomes. - Each warning/error explains the available intervention path. - Users can distinguish critical blockers from non-critical review items. - The workflow communicates what has already been reviewed and what still needs attention. ## Notes / Decisions This is partly UX copy and partly workflow-state design. It should align with the broader workflow/guided UI direction.
Author
Owner

A large local ReviewSendPage refactor partially improves stage presentation, but no accepted vocabulary/intervention matrix or focused UI tests exist. This is now a P1 Campaign pilot for the whole-system interface-pattern pass; implementation should follow the agreed placement, wording, and intervention patterns.

A large local `ReviewSendPage` refactor partially improves stage presentation, but no accepted vocabulary/intervention matrix or focused UI tests exist. This is now a P1 Campaign pilot for the whole-system interface-pattern pass; implementation should follow the agreed placement, wording, and intervention patterns.
Author
Owner

Codex State: done

Summary

  • The five-stage workflow now distinguishes critical blockers, individual review, and group review, with reviewed and remaining counts bound to the current build.
  • Every validation/build warning or blocker names the required action, responsible role, and destination through Core ActionBlockerHint; completed review now produces a completed stage instead of retaining a warning solely from historical counters.

Changed Files

  • webui/src/features/campaigns/review/ReviewWorkflowGuidance.tsx
  • webui/src/features/campaigns/review/reviewProgress.ts
  • webui/src/features/campaigns/ReviewSendPage.tsx
  • src/govoplan_campaign/backend/manifest.py
  • docs/CAMPAIGN_HANDBOOK.md

Verification

  • npm run test:review-workflow: 3 state-model tests and UI structure contract passed
  • npm run test:review-preview-ui: passed
  • pytest -q tests/test_documentation.py: 19 passed
  • Core WebUI tsc --noEmit and structural i18n audit: passed

Next / Blocked

  • Delivered in Campaign 1d6c745 and Core 70fc6da.
## Codex State: done ### Summary - The five-stage workflow now distinguishes critical blockers, individual review, and group review, with reviewed and remaining counts bound to the current build. - Every validation/build warning or blocker names the required action, responsible role, and destination through Core ActionBlockerHint; completed review now produces a completed stage instead of retaining a warning solely from historical counters. ### Changed Files - `webui/src/features/campaigns/review/ReviewWorkflowGuidance.tsx` - `webui/src/features/campaigns/review/reviewProgress.ts` - `webui/src/features/campaigns/ReviewSendPage.tsx` - `src/govoplan_campaign/backend/manifest.py` - `docs/CAMPAIGN_HANDBOOK.md` ### Verification - `npm run test:review-workflow: 3 state-model tests and UI structure contract passed` - `npm run test:review-preview-ui: passed` - `pytest -q tests/test_documentation.py: 19 passed` - `Core WebUI tsc --noEmit and structural i18n audit: passed` ### Next / Blocked - Delivered in Campaign 1d6c745 and Core 70fc6da.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-campaign#63