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

Queue mobile issue captures while offline and sync on reconnect #232

New Issue
Closed
opened 2026-08-07 21:47:48 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-07 21:47:48 +00:00
Member
Copy Link

User problem

The installed dashboard launches offline and restores My Work, but New issue still posts immediately. A disconnected mobile user can preserve only one draft and must manually retry it before capturing another item.

Vertical slice

Add a bounded durable issue outbox that preserves each planned issue and stable idempotency key, clears the composer after enqueue, exposes queued/needs-attention cards in Drafts, and sequentially syncs in the foreground on reconnect. Do not cache mutation requests.

Acceptance criteria

  • Two offline captures survive reload as distinct Drafts cards.
  • Reconnect posts each item once with its original Idempotency-Key and removes only confirmed creations.
  • Network/5xx failures remain queued; permanent validation failures become Needs attention and preserve editable fields.
  • Send now, Edit, and Discard are touch-safe at 320px width and announce outcomes through aria-live.
  • Existing issue creation, draft recovery, and service-worker behavior remain covered and green.

Non-duplication evidence

Issue history covers mobile creation (#159), idempotent retry (#177), draft discovery (#211), share capture (#223), offline shell (#226), and read-only snapshots (#228), but no multi-item offline mutation outbox or reconnect synchronization.

## User problem The installed dashboard launches offline and restores My Work, but New issue still posts immediately. A disconnected mobile user can preserve only one draft and must manually retry it before capturing another item. ## Vertical slice Add a bounded durable issue outbox that preserves each planned issue and stable idempotency key, clears the composer after enqueue, exposes queued/needs-attention cards in Drafts, and sequentially syncs in the foreground on reconnect. Do not cache mutation requests. ## Acceptance criteria - Two offline captures survive reload as distinct Drafts cards. - Reconnect posts each item once with its original Idempotency-Key and removes only confirmed creations. - Network/5xx failures remain queued; permanent validation failures become Needs attention and preserve editable fields. - Send now, Edit, and Discard are touch-safe at 320px width and announce outcomes through aria-live. - Existing issue creation, draft recovery, and service-worker behavior remain covered and green. ## Non-duplication evidence Issue history covers mobile creation (#159), idempotent retry (#177), draft discovery (#211), share capture (#223), offline shell (#226), and read-only snapshots (#228), but no multi-item offline mutation outbox or reconnect synchronization.
timmy was assigned by rockachopa 2026-08-07 21:47:48 +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#232
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?