Issue notifications — subscriptions per integration
You subscribe to a source, not an individual issue. For each subscription, set a priority threshold and which events you want to hear about.
Subscribe to a source, not an issue
The module has no “follow” button for an individual issue. A subscription covers an integration — all issues from that source.
Open subscriptions using the bell in the toolbar above the list.
Step by step — create a subscription
- Go to Tools → Issues.
- Click the bell above the list. The Issue notification subscriptions window opens.
- Under Your subscriptions, see what you already have. If the list is empty, the message says “You don’t have any subscriptions yet. Add one below to start receiving notifications.”
- Scroll to Add subscription and choose a channel under Integration source. The message “You are subscribed to all available integrations.” means there are none left to add.
- Set Minimum priority. You receive nothing below this threshold.
- To hear only about blocking issues, enable Blocking issues only. Remember that no process currently creates these (Where issues come from and how they close automatically); with this switch enabled, you will get nothing.
- Under Notify me when: enable or disable three independent events: New issue created, Issue resolved, and Issue escalated.
- Under Notification channels: choose In-app notifications, Email notifications, or both.
- Click Subscribe.
- Make sure the new entry appears under Your subscriptions, then close the window.
Subscription settings
| Setting | Purpose |
|---|---|
| Integration source | Which source you follow |
| Minimum priority | Nothing below this threshold is sent |
| Blocking issues only | Limits notifications to blocking issues |
| New issue created / Issue resolved / Issue escalated | Three independent event switches |
| Notification channels | In-app and/or email |
Defaults: minimum priority 1, all three events enabled, in-app notifications on and email off.
Who receives a notification
Each time, it goes to:
- the person assigned to the issue;
- subscribers to the source, according to their thresholds and switches;
- all company administrators, if the issue is blocking or has priority 4 or 5.
The third point matters when setting priorities: raising an issue to 4 does not just change its position in the list — it also notifies the entire administration team.
An issue nobody hears about
A combination can result in a notification reaching nobody: no source, no assignee, not blocking, and priority 3 or lower. The row is created and waits until someone checks the list.
That is why reviewing the list is essential; notifications do not cover everything.
Update notifications
When the occurrence count increases, an update notification is sent. You cannot disable it in the subscription settings; there is no switch for it. The only option is to turn off this type of notification in account settings (Notifications — the bell, email, and “Do not disturb” mode).
An issue recurring every minute can flood your inbox this way.
Automatic closure does not notify
When the system closes an issue because the cause has gone away, it does not send a resolution notification (Where issues come from and how they close automatically).
Global settings are elsewhere
Muting, the master switch, and disabling entire notification types are in account settings (Notifications — the bell, email, and “Do not disturb” mode). They apply on top of subscriptions.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo