notify: steps added to a job you own #93
Labels
No labels
adr
android
area/calendar
area/design-system
area/i18n
area/jobs
area/offline
area/server
area/testing
bug
ci
duplicate
enhancement
help wanted
invalid
notifications
question
reliability
security
severity/low
severity/medium
tracking
web
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
eagraiclainne/app#93
Loading…
Reference in a new issue
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?
A manager can attach steps (and step rewards, ADR-0025) to a job someone else owns — the owner finds out by opening the job. The work they signed up for grew silently.
Add a
STEP_ADDED-shaped emission (or reuse a kind — decide during design) minted atItemService/Createwhenparent_uidnames a job whose owner is not the actor. The sub-task inherits the parent's owner, so the recipient is the parent's owner. Batch-consideration: several steps added in one sitting should not fire N banners — maybe the first per job per hour, or accept the noise for a family-sized install.Usual kind plumbing: proto enum, notify method, en+ga messages, webhook decorator, web push-preference checkbox + PUSH_KINDS entry, Android channel.
Follow-up from the event-notifications audit (PR #90).
Decision (2026-08-16): accept the noise — one banner per step, no dedup window. Family-scale install; note the choice in the commit body.
mainto v1.5.0