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

Select updates to mark read from mobile My Work #545

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

Problem

The Updates queue currently offers only one-at-a-time acknowledgement or “mark all visible read.” Mobile operators cannot clear routine updates as a subset while preserving important unread items, causing repetitive taps or accidental loss of the unread work signal.

Evidence on origin/main@23c8e57: frontend/dashboard.js derives the sticky action from every visible notification and frontend/index.html exposes no selection mode. Historical issue #141 implemented all-visible acknowledgement, not selective triage; no open/closed issue or recent commit adds subset selection.

Acceptance criteria

  • Updates filter offers an accessible Select updates mode without mutating Gitea.
  • Update cards expose 44px checkbox targets with descriptive labels; selected count is announced live.
  • Confirmed bulk action sends only selected, deduplicated IDs, bounded to 50.
  • Successful items disappear; failed selected items remain selected for retry; unselected items stay unread.
  • Cancel/filter changes clear transient selection.
  • The sticky action remains phone-usable above safe-area/mobile navigation.
  • Behavioral tests cover selection, bounds, confirmation payload, partial failure, and cancel.
## Problem The Updates queue currently offers only one-at-a-time acknowledgement or “mark all visible read.” Mobile operators cannot clear routine updates as a subset while preserving important unread items, causing repetitive taps or accidental loss of the unread work signal. Evidence on `origin/main@23c8e57`: `frontend/dashboard.js` derives the sticky action from every visible notification and `frontend/index.html` exposes no selection mode. Historical issue #141 implemented all-visible acknowledgement, not selective triage; no open/closed issue or recent commit adds subset selection. ## Acceptance criteria - Updates filter offers an accessible Select updates mode without mutating Gitea. - Update cards expose 44px checkbox targets with descriptive labels; selected count is announced live. - Confirmed bulk action sends only selected, deduplicated IDs, bounded to 50. - Successful items disappear; failed selected items remain selected for retry; unselected items stay unread. - Cancel/filter changes clear transient selection. - The sticky action remains phone-usable above safe-area/mobile navigation. - Behavioral tests cover selection, bounds, confirmation payload, partial failure, and cancel.
timmy closed this issue 2026-08-11 06:03:13 +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
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#545
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?