[Feature] Mark all non-critical campaign review items as reviewed #64

New Issue

2026-07-14T20:08:40+02:00

zemion commented

2026-07-14 20:08:40 +02:00

Problem / User Need

In Build and review, operators need a bulk action to mark all non-critical review items as reviewed while preserving blockers and critical findings.

Acceptance Criteria

A bulk action marks only non-critical review items as reviewed.
Critical errors/blockers are excluded from the bulk action and remain visible.
The action confirms the number and category of items affected before applying, if destructive or audit-relevant.
Review state changes are persisted and reflected in the review summary.

## Problem / User Need In Build and review, operators need a bulk action to mark all non-critical review items as reviewed while preserving blockers and critical findings. ## Acceptance Criteria - A bulk action marks only non-critical review items as reviewed. - Critical errors/blockers are excluded from the bulk action and remain visible. - The action confirms the number and category of items affected before applying, if destructive or audit-relevant. - Review state changes are persisted and reflected in the review summary.

zemion added the area/api codex/ready module/campaign

labels 2026-07-29 14:15:05 +02:00

zemion commented

2026-07-31 15:20:26 +02:00

Closing as complete.

The review completion path now bulk-accepts only non-blocking warning and excluded rows. Blocked/failed rows prevent completion, while needs_review rows still require an explicit per-message review decision. The UI displays the affected count and requires confirmation; persisted state records the actor/build token and the route emits campaign.message_review_updated audit evidence.

Verification on 2026-07-31:

ApiSmokeTests.test_non_blocking_review_conditions_can_be_accepted_in_bulk passed.
Full linked Core WebUI production build passed.

Closing as complete. The review completion path now bulk-accepts only non-blocking `warning` and `excluded` rows. Blocked/failed rows prevent completion, while `needs_review` rows still require an explicit per-message review decision. The UI displays the affected count and requires confirmation; persisted state records the actor/build token and the route emits `campaign.message_review_updated` audit evidence. Verification on 2026-07-31: - `ApiSmokeTests.test_non_blocking_review_conditions_can_be_accepted_in_bulk` passed. - Full linked Core WebUI production build passed.

zemion closed this issue

2026-07-31 15:20:26 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-campaign#64