Closed
Bug 1337892
Opened 8 years ago
Closed 5 years ago
better change notifications
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
MOVED
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [lang=python])
Currently we have an extremely simplistic change notification system. For certain tables, we send e-mail to a mailing list whenever a change to them is made. This has turned out to be extremely spammy, and likely goes unread most of the time.
I think a better change notification system has at least these two requirements:
- Ability to subscribe to some types of changes but not others.
-- Product and Channel seem like the most obvious filter we'd want. Possibly being able to filter on object (eg: Rule, Release, etc.) would be useful too.
- Self serve subscriptions
There's probably other considerations that I haven't thought of.
|
Reporter | |
Comment 1•5 years ago
|
||
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → MOVED
|
||
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•