A separate pending queue for admins adding several games #749

New issue

Open

opened 2026-06-12 12:37:55 -05:00 by Veilor · 0 comments

Veilor commented

2026-06-12 12:37:55 -05:00

Member

Copy link

The admin Add Game workflow needs a separate pending queue when an admin creates the same game for multiple platforms at once.

Today, selecting several platforms creates several game records immediately from one shared set of form values. That is fast, but it also means each platform copy gets the same box art, release dates, publishers, and other metadata even when those details should differ by platform. Multi-platform adds should be held for review so admins can fix each platform-specific record before publishing, while single-platform adds should continue to publish through the normal direct flow.

Scope

Detect admin Add Game submissions that select more than one platform.
Route multi-platform submissions into a dedicated pending multi-platform queue instead of publishing the generated game records immediately.
Keep single-platform Add Game submissions on the current immediate-create path.
Provide an admin queue page or queue section for multi-platform pending game adds.
Provide an admin review/edit workflow for each platform-specific pending record before it is published.
Allow admins to correct platform-specific metadata such as box art, release dates, publishers, developers, composers, ratings, genre selections, website, source URL, and description before publishing.
Preserve the shared base data from the original add form so admins do not need to re-enter common fields for every platform.
Add publish/reject or publish/cancel behavior for pending multi-platform batches.
Ensure pending multi-platform records are not visible on public game pages, search results, lists, feeds, or user-facing counts until published.

Acceptance Criteria

Submitting Add Game with exactly one selected platform creates the game immediately as it does today.
Submitting Add Game with two or more selected platforms creates a pending multi-platform batch instead of live games.
The admin receives a clear success message that the multi-platform batch was queued for review.
Admin users can view pending multi-platform batches separately from normal published games.
Admin users can review every platform selected in the batch and edit the per-platform game data before publishing.
Each platform entry can have its own box art, release dates, publishers, developers, composers, ratings, genre selections, website, source URL, and description.
Publishing one platform entry creates or exposes the correct game record for that platform only.
Publishing an entire reviewed batch creates or exposes one game record per selected platform with the edited platform-specific values.
Pending multi-platform entries do not appear publicly until published.
Rejected or canceled pending multi-platform entries do not create public game records.
Validation errors return admins to the review form with their edited values preserved.
Authorization matches the existing admin game-management permissions.
The UI supports light/dark mode and follows the existing admin dashboard patterns.

Test Coverage Required

Feature tests proving single-platform Add Game submissions still create a live game immediately.
Feature tests proving multi-platform Add Game submissions create pending queue records and do not publish live games immediately.
Feature tests for listing pending multi-platform batches in the admin queue.
Feature tests for reviewing and editing per-platform pending records, including box art, release dates, publishers, and other metadata.
Feature tests for publishing one pending platform entry and for publishing an entire reviewed batch.
Feature tests proving pending, rejected, or canceled entries are hidden from public game pages, search/list surfaces, and counts until published.
Authorization tests for guest, non-admin, and admin access to the pending multi-platform queue and review actions.
Validation tests for required fields, platform IDs, release date formats, image uploads, and preservation of edited form data after errors.
Run the focused affected tests, then run vendor/bin/pint --dirty --format agent before closing the issue.

Progress Checklist

Admin Add Game form supports selecting one or more platforms
Current multi-platform submissions create one game per selected platform from shared form data
Add persistence for pending multi-platform add batches and per-platform pending records
Detect multi-platform Add Game submissions and queue them instead of immediately publishing games
Preserve the current immediate-create behavior for single-platform submissions
Add an admin queue page or queue section for pending multi-platform adds
Add review/edit forms for per-platform pending records
Add publish and reject/cancel actions for pending entries or batches
Ensure pending entries are excluded from all public game surfaces until published
Add success, empty, validation, and authorization states for the admin workflow
Add focused feature tests for queueing, review, publishing, visibility, validation, and authorization
Run focused tests and Pint before closing the issue

The admin Add Game workflow needs a separate pending queue when an admin creates the same game for multiple platforms at once. Today, selecting several platforms creates several game records immediately from one shared set of form values. That is fast, but it also means each platform copy gets the same box art, release dates, publishers, and other metadata even when those details should differ by platform. Multi-platform adds should be held for review so admins can fix each platform-specific record before publishing, while single-platform adds should continue to publish through the normal direct flow. ## Scope - Detect admin Add Game submissions that select more than one platform. - Route multi-platform submissions into a dedicated pending multi-platform queue instead of publishing the generated game records immediately. - Keep single-platform Add Game submissions on the current immediate-create path. - Provide an admin queue page or queue section for multi-platform pending game adds. - Provide an admin review/edit workflow for each platform-specific pending record before it is published. - Allow admins to correct platform-specific metadata such as box art, release dates, publishers, developers, composers, ratings, genre selections, website, source URL, and description before publishing. - Preserve the shared base data from the original add form so admins do not need to re-enter common fields for every platform. - Add publish/reject or publish/cancel behavior for pending multi-platform batches. - Ensure pending multi-platform records are not visible on public game pages, search results, lists, feeds, or user-facing counts until published. ## Acceptance Criteria - Submitting Add Game with exactly one selected platform creates the game immediately as it does today. - Submitting Add Game with two or more selected platforms creates a pending multi-platform batch instead of live games. - The admin receives a clear success message that the multi-platform batch was queued for review. - Admin users can view pending multi-platform batches separately from normal published games. - Admin users can review every platform selected in the batch and edit the per-platform game data before publishing. - Each platform entry can have its own box art, release dates, publishers, developers, composers, ratings, genre selections, website, source URL, and description. - Publishing one platform entry creates or exposes the correct game record for that platform only. - Publishing an entire reviewed batch creates or exposes one game record per selected platform with the edited platform-specific values. - Pending multi-platform entries do not appear publicly until published. - Rejected or canceled pending multi-platform entries do not create public game records. - Validation errors return admins to the review form with their edited values preserved. - Authorization matches the existing admin game-management permissions. - The UI supports light/dark mode and follows the existing admin dashboard patterns. ## Test Coverage Required - Feature tests proving single-platform Add Game submissions still create a live game immediately. - Feature tests proving multi-platform Add Game submissions create pending queue records and do not publish live games immediately. - Feature tests for listing pending multi-platform batches in the admin queue. - Feature tests for reviewing and editing per-platform pending records, including box art, release dates, publishers, and other metadata. - Feature tests for publishing one pending platform entry and for publishing an entire reviewed batch. - Feature tests proving pending, rejected, or canceled entries are hidden from public game pages, search/list surfaces, and counts until published. - Authorization tests for guest, non-admin, and admin access to the pending multi-platform queue and review actions. - Validation tests for required fields, platform IDs, release date formats, image uploads, and preservation of edited form data after errors. - Run the focused affected tests, then run `vendor/bin/pint --dirty --format agent` before closing the issue. ## Progress Checklist - [x] Admin Add Game form supports selecting one or more platforms - [x] Current multi-platform submissions create one game per selected platform from shared form data - [ ] Add persistence for pending multi-platform add batches and per-platform pending records - [ ] Detect multi-platform Add Game submissions and queue them instead of immediately publishing games - [ ] Preserve the current immediate-create behavior for single-platform submissions - [ ] Add an admin queue page or queue section for pending multi-platform adds - [ ] Add review/edit forms for per-platform pending records - [ ] Add publish and reject/cancel actions for pending entries or batches - [ ] Ensure pending entries are excluded from all public game surfaces until published - [ ] Add success, empty, validation, and authorization states for the admin workflow - [ ] Add focused feature tests for queueing, review, publishing, visibility, validation, and authorization - [ ] Run focused tests and Pint before closing the issue

Veilor added the

Rows
Columns