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

Open Following alerts directly in changed-first review #1317

New Issue
Closed
opened 2026-08-23 18:23:56 +00:00 by timmy · 0 comments
timmy commented 2026-08-23 18:23:56 +00:00
Owner
Copy Link

Problem

Following push alerts target #/my-work/following, but the work router does not recognize that route, so tapping the alert cannot complete the advertised changed-first review handoff.

User outcome

A mobile operator tapping a Following alert reaches the authoritative watched-items state and immediately enters the first unseen change. If no change remains or refresh fails, Following opens with a truthful empty/retry state.

Acceptance criteria

  • #/my-work/following is a supported, Back-safe queue route.
  • Route activation loads Following and starts changed-first review exactly once.
  • Empty/stale alerts open the Following sheet without acknowledging anything.
  • Failed refresh opens Following with retry guidance.
  • Push payload remains generic and privacy-safe.
  • Behavioral route/controller and packaged mobile tests cover the alert-to-review journey.
## Problem Following push alerts target `#/my-work/following`, but the work router does not recognize that route, so tapping the alert cannot complete the advertised changed-first review handoff. ## User outcome A mobile operator tapping a Following alert reaches the authoritative watched-items state and immediately enters the first unseen change. If no change remains or refresh fails, Following opens with a truthful empty/retry state. ## Acceptance criteria - `#/my-work/following` is a supported, Back-safe queue route. - Route activation loads Following and starts changed-first review exactly once. - Empty/stale alerts open the Following sheet without acknowledging anything. - Failed refresh opens Following with retry guidance. - Push payload remains generic and privacy-safe. - Behavioral route/controller and packaged mobile tests cover the alert-to-review journey.
timmy self-assigned this 2026-08-23 18:23: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#1317
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?