stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Queue offline Today reviews and continue to the next item #423

New Issue
Closed
opened 2026-08-09 19:51:09 +00:00 by timmy · 0 comments
timmy commented 2026-08-09 19:51:09 +00:00
Owner
Copy Link

User problem

Completing a cached pull-request review offline currently queues the review but leaves the Today item and sheet in place. The operator must perform a second planning action before continuing, unlike the online review flow.

Scope

When an offline review is opened from an active Today session, present Queue review & next. After durable outbox admission succeeds, remove the review from Today, queue plan sync, and advance to the next item. Keep non-Today offline review behavior unchanged. If queue admission fails, preserve Today and the draft. If Today persistence fails after queue admission, do not advance and clearly report the partial success.

Acceptance criteria

  • The action is labelled Queue review & next only for an active Today session; otherwise it remains Queue review for reconnect.
  • Durable review admission happens before any Today mutation.
  • Successful admission removes the current Today item, queues plan sync, and advances exactly once.
  • Local Today persistence failure leaves the session on the current item and reports that the review is queued but Today still needs completion.
  • Reload retains the queued review and the advanced Today checkpoint.
  • Touch target remains at least 44px with no mobile overflow.
  • Behavioral tests cover success, admission failure, persistence failure, and non-Today behavior.

Closes the workflow gap between #419 and #421; neither issue integrated the two completed flows.

## User problem Completing a cached pull-request review offline currently queues the review but leaves the Today item and sheet in place. The operator must perform a second planning action before continuing, unlike the online review flow. ## Scope When an offline review is opened from an active Today session, present **Queue review & next**. After durable outbox admission succeeds, remove the review from Today, queue plan sync, and advance to the next item. Keep non-Today offline review behavior unchanged. If queue admission fails, preserve Today and the draft. If Today persistence fails after queue admission, do not advance and clearly report the partial success. ## Acceptance criteria - The action is labelled `Queue review & next` only for an active Today session; otherwise it remains `Queue review for reconnect`. - Durable review admission happens before any Today mutation. - Successful admission removes the current Today item, queues plan sync, and advances exactly once. - Local Today persistence failure leaves the session on the current item and reports that the review is queued but Today still needs completion. - Reload retains the queued review and the advanced Today checkpoint. - Touch target remains at least 44px with no mobile overflow. - Behavioral tests cover success, admission failure, persistence failure, and non-Today behavior. Closes the workflow gap between #419 and #421; neither issue integrated the two completed flows.
timmy self-assigned this 2026-08-09 19:51:09 +00:00
timmy closed this issue 2026-08-09 20:06:05 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#423
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?