Email notifications
The four email notifications GVenta Kanban Board can send, who receives each one, the per-user toggles that control them, watching, and the 08:00 daily digest.
Documented from GVenta Kanban Board version 2.1.15.
GVenta Kanban Board can email you when stories you care about change, when you are assigned work, when someone comments, and once a day with a digest. Every one of these is an independent per-user toggle, and none of them can ever interfere with the action that triggered it.
Watching a story
Most notifications are tied to watching. A watcher is a user subscribed to a story’s email notifications. You must be watching a story to be alerted about it.
Commenting on a story subscribes you automatically. Watching and unwatching are also available through the API (POST and DELETE /api/v1/stories/{id}/watch, and GET /api/v1/stories/{id}/watchers to see who is watching).
Your notification preferences
Open your profile from your avatar and name in the top header. The profile page shows your name and email read-only, lets you upload or remove your avatar (a new avatar appears everywhere immediately), and carries the Email notification preferences panel: four toggle switches, each with an explanatory caption.
| Toggle | Fires when |
|---|---|
| Story updated | Any field on a story you watch changes |
| Assignee changed | You are assigned to a story |
| New comment | Someone comments on a story you watch |
| Daily digest | One email per day summarizing activity on your watched stories |
The panel states the prerequisite plainly: you must be watching a story to be alerted about it. The exception is Assignee changed, which is about you personally rather than about a watched story.
The four emails
All four emails share a branded HTML shell with a footer explaining why you received it and linking to your preferences page.
| Trigger | Recipients | Suppression rules |
|---|---|---|
| Story updated | Watchers with Story updated enabled | The acting user is always excluded. If the only change was the assignee, this email is suppressed in favor of the assignment email. The body lists each changed field as old → new. |
| Story assigned | The new assignee, if they have Assignee changed enabled | Not sent when the story is unassigned or the user has no email address. |
| New comment | Watchers with New comment enabled | The comment’s author is excluded. The body quotes the first 300 characters of the comment. |
| Daily digest | Every user with Daily digest enabled | Sent by a scheduled job at 08:00 daily. Aggregates the top 20 watched stories with activity in the last 24 hours, counting only activity by other people. Users with no qualifying activity are skipped entirely. |
What triggers them
- Story updated and Story assigned fire from the story edit form and from story updates through the API. The API computes a field-level change set, writes it to the activity log and dispatches the same emails.
- New comment fires whenever a comment is posted, from the composer or the API.
- Daily digest runs on its own schedule, completely outside any user action.
Why it matters: The digest only tells you what other people did to the stories you watch, and it skips you entirely on quiet days, so it stays worth opening.
Emails never break the triggering action
Emails are sent through SendGrid with a 10-second timeout. If sending fails, the failure is written to the error log and the request that triggered it completes normally. Saving a story, reassigning it or posting a comment never fails because an email could not be delivered.
Related pages
- Comments and mentions — how commenting subscribes you as a watcher.
- Stories, epics and tasks — the assignment email on save.
- Integrations — SendGrid and its failure behavior.