Story #14435
open[Navigation] Investigation - Notification system
0%
Description
Notifications:
- <User name> shared <name> with you.
- <User name> shared <name> to group <group name>.
- <Process name> is completed.
- <Process name> failed.
- <User name> uploaded collection <name> to Project <name>
- <User name> added/removed/renamed file in collection <name>
User should be able to subscribe to a project tree and select types of objects/events they are interested in.
How much detail should the notification contain?
Don't want to spam user with lots of changes, should be able to batch notification of certain kinds of changes.
Notification should go to email, Workbench 2.
Need an inbox (probably a new database table) which the system can dump messages into
Need a system for filtering what kinds of notifications user is interested in.
Contents of your inbox consists of log ids?
API response on inbox includes a uuid of a log event and a HTML string which is the text message to be displayed to the user.
Brett: wb2 and email display are so different that maybe they should have their own rendering.
Updated by Chrystian Klingenberg about 6 years ago
- Target version set to sprint 12
Updated by Chrystian Klingenberg about 6 years ago
- Target version changed from sprint 12 to sprint 13 (lucky number)
Updated by Chrystian Klingenberg about 6 years ago
- Target version deleted (
sprint 13 (lucky number))