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

Bulk acknowledge unread updates from mobile My Work #141

New Issue
Closed
opened 2026-08-06 21:49:18 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-06 21:49:18 +00:00
Member
Copy Link

Problem

The deployed dashboard currently exposes dozens of unread updates, but mobile My Work requires one request and one rerender per update. Operators cannot clear a backlog efficiently from a phone. Existing issues #133/#135 added unread cards and single-item acknowledgement only; historical issue/commit review found no bulk, batch, mark-all, or triage implementation.

Vertical slice

Add a thumb-reachable bulk acknowledgement flow to the Updates view, backed by a bounded batch API with partial-failure retry.

Acceptance criteria

  • Updates view shows Mark all N updates read only when actionable unread updates are visible.
  • Confirmation prevents accidental bulk mutation; duplicate activation is single-flight.
  • API accepts unique positive thread IDs, caps batches at 50, and returns successful and failed IDs without losing partial progress.
  • Successful standalone updates disappear; assigned/review work remains without its unread badge.
  • Partial failures remain actionable and retry submits only failed IDs.
  • Mobile action is sticky, safe-area aware, no wider than its container, and at least 44px high.
  • Focus and aria-live status communicate progress and completion.
  • Behavioral tests cover validation, partial failure, single-flight, and mobile markup.
## Problem The deployed dashboard currently exposes dozens of unread updates, but mobile My Work requires one request and one rerender per update. Operators cannot clear a backlog efficiently from a phone. Existing issues #133/#135 added unread cards and single-item acknowledgement only; historical issue/commit review found no bulk, batch, mark-all, or triage implementation. ## Vertical slice Add a thumb-reachable bulk acknowledgement flow to the Updates view, backed by a bounded batch API with partial-failure retry. ## Acceptance criteria - Updates view shows `Mark all N updates read` only when actionable unread updates are visible. - Confirmation prevents accidental bulk mutation; duplicate activation is single-flight. - API accepts unique positive thread IDs, caps batches at 50, and returns successful and failed IDs without losing partial progress. - Successful standalone updates disappear; assigned/review work remains without its unread badge. - Partial failures remain actionable and retry submits only failed IDs. - Mobile action is sticky, safe-area aware, no wider than its container, and at least 44px high. - Focus and aria-live status communicate progress and completion. - Behavioral tests cover validation, partial failure, single-flight, and mobile markup.
timmy was assigned by rockachopa 2026-08-06 21:49:18 +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#141
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?