Comments & notifications
Writing comments, @mentions and reactions, who is e-mailed about what, notification schemes, browser push, webhooks and how to find out why a message was not sent.
Commenting
Open an issue, press m (or click Comments in the activity section) and write. The comment box is the same Markdown editor as the description: preview, tables, task lists, pasted screenshots and attachments.
- @mention — type
@and a name. The person is notified, even if they are not watching the issue. - Reply — comments are threaded; replies show Replying to the comment above.
- Edit and delete — you can change or remove your own comments; administrators can moderate others’ if the permission scheme gives them the right.
- Reactions — add an emoji reaction instead of a “+1” comment (a project or an administrator can switch reactions off).
- Internal notes — on service desk requests, a comment can be internal and is then hidden from the customer. See Queues, SLA & email.
Watching
Press Watch on an issue to receive its updates, and Stop watching to leave. The details panel lists the watchers. Bulk change can watch or unwatch a whole selection at once.
What triggers a notification
| Event | Who can be told |
|---|---|
| Issue created | assignee, reporter, watchers, project lead |
| Issue updated | assignee, reporter, watchers, project lead (not the person who made the change) |
| Issue transitioned (status change) | same people |
| Issue assigned | the new assignee and the usual recipients |
| Comment added | assignee, reporter, watchers, project lead, and anyone @mentioned |
| Issue deleted, sprint started, sprint closed | as configured in the scheme |
The actual list for your instance is the notification scheme a project uses.
Notification schemes (administrators)
Administration → Notifications lists the schemes. A scheme answers, for each event, who gets an e-mail: the Assignee, the Reporter, the Project Lead, the Watchers, the Current User or All Admins. Create a scheme with New Scheme, tick the recipients per event, save, and choose the scheme for a project under its Schemes tab. Changes apply to future events only.
The Notification helper (Administration, issues section) answers “would this user get an e-mail for this event on this issue, and why?” — start there when someone says they never got a message.
E-mail goes through the SMTP server an administrator configures under Administration → System (mail server). Messages are plain, link back to the issue and are sent with user-supplied text escaped, so a comment cannot inject markup. Service desk customers get their own messages — request created, comment added, status changed, CSAT survey — described in Queues, SLA & email.
Browser push
Under Personal settings → Push notifications allow notifications for this browser. You then get a pop-up for issues assigned to you, @mentions and comments on issues you follow, even when Veqsio is not open. Disable it in the same place or in your browser’s site settings.
Webhooks and chat
Beyond e-mail, an administrator can send events to other systems:
- Webhooks (Administration → Notifications): signed (HMAC) HTTP calls with retries and a delivery log.
- Slack and Microsoft Teams: per project (Project settings → Slack & Teams) and as an instance default (Administration → Integrations).
- AI agents and plugins receive signed webhook events too; see API & integrations.
Reducing noise
- Stop watching issues you no longer care about.
- Ask your administrator to remove “Issue updated” e-mail from the scheme and keep comments and assignments.
- Use push for what is urgent and a daily filter digest for everything else.