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

Surface deadline-critical assigned work in mobile Attention #273

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

Problem

The mobile Work dock and Attention queue count only unread updates and requested reviews, even though My Work already ranks assigned P0/critical, overdue, and due-today issues as urgent. Operators can therefore see a zero badge while deadline-critical work is hidden under All.

Vertical slice

Define one canonical attention predicate covering unread updates, requested reviews, assigned P0/critical work, assigned overdue work, and assigned due-today work. Reuse it for filtering and counts so overlapping reasons are deduplicated. Preserve existing one-tap mobile routing and expose the urgency reason in the queue.

Acceptance criteria

  • P0/critical, overdue, and due-today issues assigned to the signed-in operator appear in Attention.
  • Unassigned deadline/priority issues and ordinary future-due assignments do not appear solely from those signals.
  • Review/update overlaps count once; filter and dock count cannot drift.
  • Date/label/content refreshes recompute membership from confirmed state.
  • Existing update/review behavior, offline read-only rendering, mobile dock accessibility, and service-worker delivery remain green.
  • Behavioral tests cover boundaries and deduplication before implementation.
## Problem The mobile Work dock and Attention queue count only unread updates and requested reviews, even though My Work already ranks assigned P0/critical, overdue, and due-today issues as urgent. Operators can therefore see a zero badge while deadline-critical work is hidden under All. ## Vertical slice Define one canonical attention predicate covering unread updates, requested reviews, assigned P0/critical work, assigned overdue work, and assigned due-today work. Reuse it for filtering and counts so overlapping reasons are deduplicated. Preserve existing one-tap mobile routing and expose the urgency reason in the queue. ## Acceptance criteria - P0/critical, overdue, and due-today issues assigned to the signed-in operator appear in Attention. - Unassigned deadline/priority issues and ordinary future-due assignments do not appear solely from those signals. - Review/update overlaps count once; filter and dock count cannot drift. - Date/label/content refreshes recompute membership from confirmed state. - Existing update/review behavior, offline read-only rendering, mobile dock accessibility, and service-worker delivery remain green. - Behavioral tests cover boundaries and deduplication before implementation.
timmy was assigned by rockachopa 2026-08-08 06:50:02 +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#273
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?