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

Queue offline issue closure and continue Today #427

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

User problem

Mobile operators can read cached Today work and queue review submissions offline, but Close & next still requires a live request. A connection loss interrupts completion and leaves the operator stuck on the current item.

Vertical slice

  • Admit an account-bound issue-close operation durably while offline.
  • Only after admission, remove the current item from Today and open the next item.
  • Deliver the close after reconnect/background sync; treat already-closed as success.
  • Surface permanent failures in Drafts with retry/discard instead of silently losing them.

Acceptance tests

  • Offline cached issue offers Queue close & next.
  • Durable admission happens before Today advances; admission failure keeps the current item.
  • Reconnect sends the close operation and confirms closed state.
  • Permanent delivery failure remains visible as needs attention.
  • Session purge removes queued private operations.

This is distinct from #391 (online Close & next), #421 (local Done & next without changing Gitea), and #423 (offline PR review delivery).

## User problem Mobile operators can read cached Today work and queue review submissions offline, but **Close & next** still requires a live request. A connection loss interrupts completion and leaves the operator stuck on the current item. ## Vertical slice - Admit an account-bound issue-close operation durably while offline. - Only after admission, remove the current item from Today and open the next item. - Deliver the close after reconnect/background sync; treat already-closed as success. - Surface permanent failures in Drafts with retry/discard instead of silently losing them. ## Acceptance tests - Offline cached issue offers Queue close & next. - Durable admission happens before Today advances; admission failure keeps the current item. - Reconnect sends the close operation and confirms closed state. - Permanent delivery failure remains visible as needs attention. - Session purge removes queued private operations. This is distinct from #391 (online Close & next), #421 (local Done & next without changing Gitea), and #423 (offline PR review delivery).
timmy self-assigned this 2026-08-09 21:26:32 +00:00
timmy closed this issue 2026-08-09 21:28:00 +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#427
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?