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

Notify mobile operators when Following changes #1313

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

User problem

Following detects unseen changes only when an operator opens Prepare Today or the Following inbox. A mobile operator who deliberately watches non-owned work still has to remember to reopen Stackchain.

Vertical slice

Add a privacy-safe, opt-in Following Web Push channel: detect a watched revision once per device, send generic lock-screen copy, and deep-link taps into the existing changed-first Following review flow. Keep the channel independent from Updates/deadline delivery and never include repository names, titles, bodies, or comments in the payload.

Acceptance criteria

  • Following alerts are explicitly opt-in per active device and can be disabled without affecting other push channels.
  • A watched item advancing revisions emits one generic alert; repeat polls at the same revision do not duplicate it.
  • Expired/revoked sessions receive nothing. Delivery checkpoints are safe across workers.
  • Notification taps open #/my-work/following; malformed payloads fall back safely.
  • Behavioral server/frontend/service-worker tests and a rendered 320x568/390x844 mobile journey pass.

Implementation must use strict RED-GREEN-REFACTOR and preserve existing notification behavior.

## User problem Following detects unseen changes only when an operator opens Prepare Today or the Following inbox. A mobile operator who deliberately watches non-owned work still has to remember to reopen Stackchain. ## Vertical slice Add a privacy-safe, opt-in Following Web Push channel: detect a watched revision once per device, send generic lock-screen copy, and deep-link taps into the existing changed-first Following review flow. Keep the channel independent from Updates/deadline delivery and never include repository names, titles, bodies, or comments in the payload. ## Acceptance criteria - Following alerts are explicitly opt-in per active device and can be disabled without affecting other push channels. - A watched item advancing revisions emits one generic alert; repeat polls at the same revision do not duplicate it. - Expired/revoked sessions receive nothing. Delivery checkpoints are safe across workers. - Notification taps open `#/my-work/following`; malformed payloads fall back safely. - Behavioral server/frontend/service-worker tests and a rendered 320x568/390x844 mobile journey pass. Implementation must use strict RED-GREEN-REFACTOR and preserve existing notification behavior.
timmy self-assigned this 2026-08-23 17:44:04 +00:00
timmy closed this issue 2026-08-23 18:02:53 +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#1313
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?