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

Snooze mobile deadline reminders from the lock screen #1102

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

Evidence

Deadline push notifications currently offer Protect Today and redundant Open Agenda actions. Tapping the notification body already opens Agenda, while delivered_local_day suppresses any further prompt that day. A reminder received during a meeting can therefore be dismissed with no way to preserve it. Existing update notifications already prove authenticated lock-screen actions can fall back safely into the app.

User flow

Replace Open Agenda with Remind in 1 hour. The service worker records a device/session-bound server snooze. At expiry, the deadline dispatcher fetches a fresh complete assigned-issue snapshot and sends a follow-up only if qualifying deadlines remain. On action failure, open Agenda rather than silently losing the reminder.

Acceptance tests

  • Deadline notifications expose Protect Today and Remind in 1 hour; body tap still opens Agenda.
  • Snooze mutation is authenticated and bound to the current subscribed device with enabled reminders.
  • No follow-up sends before expiry.
  • At expiry, a fresh complete snapshot sends one privacy-safe follow-up when deadlines remain, then clears snooze.
  • Resolved deadlines clear the expired snooze without sending; incomplete snapshots fail closed and retain it for retry.
  • Failed lock-screen mutation opens Agenda.
  • Existing timezone, horizon, local-day dedupe, authorization, and fanout behavior remains green.

Non-duplication

All 553 historical issue titles and recent commits were checked. Existing deadline work covers delivery, timezone/horizon, polling, and Protect Today, but no title or commit implements snooze/remind-later behavior.

## Evidence Deadline push notifications currently offer **Protect Today** and redundant **Open Agenda** actions. Tapping the notification body already opens Agenda, while `delivered_local_day` suppresses any further prompt that day. A reminder received during a meeting can therefore be dismissed with no way to preserve it. Existing update notifications already prove authenticated lock-screen actions can fall back safely into the app. ## User flow Replace **Open Agenda** with **Remind in 1 hour**. The service worker records a device/session-bound server snooze. At expiry, the deadline dispatcher fetches a fresh complete assigned-issue snapshot and sends a follow-up only if qualifying deadlines remain. On action failure, open Agenda rather than silently losing the reminder. ## Acceptance tests - Deadline notifications expose **Protect Today** and **Remind in 1 hour**; body tap still opens Agenda. - Snooze mutation is authenticated and bound to the current subscribed device with enabled reminders. - No follow-up sends before expiry. - At expiry, a fresh complete snapshot sends one privacy-safe follow-up when deadlines remain, then clears snooze. - Resolved deadlines clear the expired snooze without sending; incomplete snapshots fail closed and retain it for retry. - Failed lock-screen mutation opens Agenda. - Existing timezone, horizon, local-day dedupe, authorization, and fanout behavior remains green. ## Non-duplication All 553 historical issue titles and recent commits were checked. Existing deadline work covers delivery, timezone/horizon, polling, and Protect Today, but no title or commit implements snooze/remind-later behavior.
timmy was assigned by rockachopa 2026-08-18 23:51:06 +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#1102
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?