Features · Notifications
Notifications, your way
An in-app inbox, a project activity feed, and email only if you want it.
Every ticket event your team cares about lands in an in-app inbox, so mentions, assignments and status changes never depend on email. Who hears about what is decided by a per-project notification scheme, and an optional SMTP email channel — off by default — delivers events immediately or as a daily digest. Mutes, snooze and a project activity feed keep the signal high and the record complete.
What you get
- In-app inbox — every notification lands in a filterable inbox — unread-only or by event type — with per-item mark-read, mark-all-read and an unread badge in the navigation.
- Per-project schemes — named rule sets map each event type to its recipients — current assignee, reporter, watchers, a project role, a named user, a user group or all project members.
- Optional email channel — SMTP delivery sits behind a server flag and stays off by default; each user picks immediate mail, a daily digest, or in-app only.
- Daily digest — one email summarises your unread notifications — up to 20 lines, laid out flat, grouped by project or grouped by event type.
- Mutes and snooze — silence one project, one event type or both — in-app and email alike — or snooze everything until a time you choose.
- Project activity feed — a chronological feed of ticket creations, comments and field changes across the whole project, each entry with actor, timestamp and old-to-new values.
Who gets notified
Each project points at a notification scheme: rules that map an event type to recipients. The built-in default notifies the reporter, current assignee and watchers on comments and status changes, the assignee on assignment, and the assignee on an SLA breach. @Mentioned users are always notified regardless of scheme rules, you are never notified about your own actions, and named users or groups are only notified when they can actually see the project. Ticket-created and ticket-updated events start with no rules, so administrators opt in deliberately.
Email on your terms
The email channel stays off until an administrator enables the server flag and configures an SMTP host. Each user then chooses immediate mail, a daily digest or in-app only. The digest is a single email of your unread notifications — capped at 20 lines with an overflow count — grouped flat, by project or by event type, and it is safe to run across multiple backend nodes without double-sending. Administrators can override each email template's subject and body using simple placeholder tokens.
Quiet when you need it
A mute silences matching events entirely, in-app and email, and it can target one project, one event type or both; an explicit mute even overrides the always-notify mention rule. Snooze pauses all notifications until a timestamp you set. When you return, the per-project activity feed holds the full ordered record of who created, commented on or changed what, so catching up does not depend on what was notified.
In practice
Default notification scheme
COMMENTED → reporter, current assignee, watchers
STATUS_CHANGED → reporter, current assignee, watchers
ASSIGNED → current assignee
SLA_BREACHED → current assignee
MENTIONED → the @mentioned users (always)See Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.