Watching and notifications
Select "Watch" on an issue to become a watcher. A watcher receives notifications about their own actions and other people's actions, including when they are also the issue's reporter or assignee. This is the only exception to the rule that the person making a change does not receive a notification about their own action. It applies equally to the interface, API and MCP.
Both settings must be enabled for delivery:
- Under Administration → Notifications, an enabled rule for the event addresses "Issue watchers". If the rule is limited to a project, the issue must belong to that project.
- The corresponding category is enabled under "Email notifications" in your profile.
Events are separate: "Issue updated" covers field edits, while "Issue status changed" covers transitions, including completion. Watching an issue does not enable company rules or override profile preferences. In the current version, disabling a profile category stops new notifications of that category in both email and Inbox.
You must still have access to the issue. Overlapping roles and matching rules produce one notification per event. A mention in a comment does not create a second notification for that comment. After selecting "Stop watching", the exception for your own actions ends; other matching rules continue to apply.
The inbox item and email show a short event summary: the changed field with its before/after values, a comment excerpt, or an attachment name and size. Long text points to the changed passage rather than an identical opening. Clearing a value is explicit. Details are captured when the change happens: a later edit does not rewrite an earlier notification.
Details take up to three lines, with up to 200 visible characters per line. When there are more changes or files, the last line counts the remaining items. An ellipsis marks shortened text; use "Open issue" to see the full content. Markdown appears as readable text without embedded images; files are not attached to the email. Older notifications without details retain the information available.
Company recipient settings
A standing administrator opens "Administration → Notifications", selects an event and, for a project event, one project or "Any project". You can use the search field to select multiple roles, users and groups: for example, the assignee, reporter, two colleagues and a support group. Changing the event or project removes incompatible choices with an explicit notice.
Rules with the same event, scope, enabled state and mandatory status appear as one card. The first five recipients appear inline; "More N" opens the remaining names above the list without moving other cards. Long lists scroll. You can open the popup with the keyboard, close it with Escape, or click outside.
Choose "Edit" to add or remove recipients. In an existing setting, each recipient has an individual enabled state. Mandatory rules cannot be disabled or removed. Different states remain separate cards; the card's toggle and delete action affect only that card's recipients. Deletion asks for confirmation.
All changes are saved together. If saving fails, no changes are applied. A rejected save leaves the selection in the form. If someone else changed the setting, reload the list and open it again. The same recipient cannot be added twice for the same event and project, even when the existing rule is off. Open the existing setting instead.
If an "Any project" rule is enabled for an event, adding the same recipient for that event to a project-specific rule is not allowed. Choose a different recipient or event, or edit the existing rule. Adding a global rule later preserves existing project rules and their states. When no choices remain, the form explains this and offers the existing setting.
Mandatory rules
Control notifications about Administrator rights can be mandatory. They cannot be disabled or deleted, and their profile category cannot be declined. If a user is a recipient in several rules, a matching mandatory rule keeps delivery mandatory. It does not enable every event or grant access to restricted issues.
Check delivery
Ask a colleague to edit a field on an issue you watch. First check that both the company rule for the issue-update event and your profile category are enabled. You receive an Inbox notification and an email summarizing the change. Status transitions use a separate event and setting.
If neither arrives, check the rule's company and project scope, event, selected recipients, your watching state, profile preference and current issue access. For your own action, the exception applies only through a matching Watchers rule. Being the reporter or assignee alone does not grant that exception.
If the Inbox notification exists but the email has not arrived, check spam and the address in your profile. Email delivery may finish after the event appears in the product. Changing rules does not resend past events. Creating duplicate rules will not retry an earlier email.