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

Reply, mark read, and continue unread updates #503

New Issue
Closed
opened 2026-08-10 17:50:12 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 17:50:12 +00:00
Owner
Copy Link

User problem

Mobile inbox triage currently requires separate reply and acknowledgement actions. Reply & next only works inside Today and deliberately leaves the update unread.

Slice

Add one thumb-friendly action that posts a reply exactly once, marks that notification read only after reply confirmation, removes it locally, and opens the next unread update. Retryable/offline failures must durably preserve the ordered reply-then-read operation; partial delivery must resume at acknowledgement without reposting.

Acceptance

  • Available on every supported unread update with a non-empty reply, independent of Today.
  • Online: exactly one reply, then exact notification acknowledgement, then next unread update.
  • Permanent reply failure leaves unread state and draft intact; no acknowledgement.
  • Reply-confirmed/read-failed retry does not repost.
  • Offline admission is durable before local advance and background delivery preserves ordering.
  • Single-flight on rapid taps; mobile target is at least 44px with no horizontal overflow.
  • Focused and full tests pass.
## User problem Mobile inbox triage currently requires separate reply and acknowledgement actions. Reply & next only works inside Today and deliberately leaves the update unread. ## Slice Add one thumb-friendly action that posts a reply exactly once, marks that notification read only after reply confirmation, removes it locally, and opens the next unread update. Retryable/offline failures must durably preserve the ordered reply-then-read operation; partial delivery must resume at acknowledgement without reposting. ## Acceptance - Available on every supported unread update with a non-empty reply, independent of Today. - Online: exactly one reply, then exact notification acknowledgement, then next unread update. - Permanent reply failure leaves unread state and draft intact; no acknowledgement. - Reply-confirmed/read-failed retry does not repost. - Offline admission is durable before local advance and background delivery preserves ordering. - Single-flight on rapid taps; mobile target is at least 44px with no horizontal overflow. - Focused and full tests pass.
timmy self-assigned this 2026-08-10 17:50:12 +00:00
timmy closed this issue 2026-08-10 18:04:36 +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#503
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?