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

Add a one-tap mobile Attention queue #244

New Issue
Closed
opened 2026-08-07 23:54:56 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-07 23:54:56 +00:00
Member
Copy Link

Product problem

Mobile users can complete unread-update and requested-review workflows inside My Work, but the thumb dock does not show incoming workload and its Work action only scrolls to the unfiltered queue. Reviews with unread updates also overlap, so adding separate counts would overstate the workload.

Vertical slice

  • Add a deduplicated Attention filter (has_update || is_review) in existing priority order.
  • Show its live count on the mobile Work dock action and hide the badge at zero.
  • One tap on Work with pending attention selects the filter and focuses My Work.
  • Keep offline snapshots read-only and compute the same queue locally.
  • Ship the changed shell atomically through the service worker.

Acceptance

  1. One unread issue, one requested review, and one review with an unread update produce 3 Attention items, not 4.
  2. At 390x844 the five dock targets remain >=44px, fixed above the safe area, without horizontal overflow; Work exposes an accessible attention count.
  3. Work selects Attention when nonempty; when empty it returns to All.
  4. Read/review completion updates the count immediately.
  5. Focused tests and the full suite pass.

Evidence / non-duplication

Current main e0bc727: existing #117/#151 implement separate reviews/updates and #236 adds the base dock. All 125 historical issue titles and recent commits were checked; none implements a unified Attention queue or Work-dock count.

## Product problem Mobile users can complete unread-update and requested-review workflows inside My Work, but the thumb dock does not show incoming workload and its Work action only scrolls to the unfiltered queue. Reviews with unread updates also overlap, so adding separate counts would overstate the workload. ## Vertical slice - Add a deduplicated Attention filter (`has_update || is_review`) in existing priority order. - Show its live count on the mobile Work dock action and hide the badge at zero. - One tap on Work with pending attention selects the filter and focuses My Work. - Keep offline snapshots read-only and compute the same queue locally. - Ship the changed shell atomically through the service worker. ## Acceptance 1. One unread issue, one requested review, and one review with an unread update produce 3 Attention items, not 4. 2. At 390x844 the five dock targets remain >=44px, fixed above the safe area, without horizontal overflow; Work exposes an accessible attention count. 3. Work selects Attention when nonempty; when empty it returns to All. 4. Read/review completion updates the count immediately. 5. Focused tests and the full suite pass. ## Evidence / non-duplication Current main `e0bc727`: existing #117/#151 implement separate reviews/updates and #236 adds the base dock. All 125 historical issue titles and recent commits were checked; none implements a unified Attention queue or Work-dock count.
timmy was assigned by rockachopa 2026-08-07 23:54:56 +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#244
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?