= role user/group receives notification
= role user/group does not receive notification
= role not included for this eventProvided you have entered a working email address for your userid in Helix Server, Swarm sends email notifications to you when various events take place. The table below shows the notifications sent if all of the project, group, and user notifications are enabled, this is the default behavior.
The system-wide default notifications can be changed by the system owner. See Global settings for details.
Many of the notifications can be disabled, this allows project, group, and user notifications to be customized to limit the number and type of notifications sent.
Legend:
| A = Author | PM = Project member or project member group |
= role user/group receives notification |
| R = Reviewer or reviewer group | PF = Project follower | = role user/group does not receive notification |
| M = Moderator or moderator group | AF = Author follower | = role not included for this event |
| GM = Group member | CA = Comment author |
| Event | Notification sent to one of these roles... | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Event by you? | A | R | M | GM | PM | PF | AF | CA | |
| A review is committed in Swarm |
|
|
|
3
|
4
|
1
|
1
|
|
|
| A review is committed outside of Swarm |
|
|
|
3
|
4
|
1
|
1
|
|
|
| A change is committed outside of Swarm (see (1) Committed change notifications) |
|
|
|
3
|
 4
|
1
|
1
|
1
|
|
| A review is started (see (2) Review start notifications) |
|
|
|
3
|
4
|
2
|
|
|
|
| A reviewer casts a vote |
|
|
5
|
|
4
|
|
|
|
|
| A review's state changes |
|
|
5
|
|
4
|
|
|
|
|
| A review's reviewers are changed |
|
|
5
|
|
4
|
|
|
|
|
| A review's files are updated |
|
|
5
|
|
4
|
|
|
|
|
| A review's automated tests have finished (see (7) Tests have finished) |
|
|
|
|
4
|
|
|
|
|
| A review's description is changed |
|
|
|
|
|
|
|
|
|
| A review comment is created (see Comment notification delay). |
|
|
5
|
|
4
|
|
|
|
6
|
| A review comment is edited (see Comment notification delay). |
|
|
5
|
|
4
|
|
|
|
6
|
| A committed change comment is created |
|
|
|
|
4
|
|
|
|
6
|
| A committed change comment is edited |
|
|
|
|
4
|
|
|
|
6
|
| Someone joins or leaves a review |
|
|
5
|
|
4
|
|
|
|
|
| Someone likes a comment you wrote |
|
|
|
|
|
|
|
|
5
|
| You like a comment you wrote |
|
|
|
|
|
|
|
|
|
Any custom modules added to Swarm may also send notifications.
Email delivery for events related to restricted changes is disabled by default. See Restricted Changes for details on how to enable restricted change notifications.
Using an @mention in a review, changelist, or comment causes the referenced userid to receive a notification and be included in any future notifications regarding the associated file or review.
When a comment is added to a job, Swarm sends a notification to users listed in user fields in the job, users @mentioned in the job description, and the authors of any associated changes.
Typically, you would not receive a notification when you @mention yourself. @mentions themselves do not trigger notifications; they inform who receives notifications. See notify_self for details on how to enable self notification.
Using an @@mention in a review, changelist, or comment causes the referenced groupid members to receive a notification and be included in any future notifications regarding the associated file or review.
When a comment is added to a job, Swarm sends a notification to groups listed in group fields in the job, groups @@mentioned in the job description, and the authors of any associated changes.
Notifications for committed changes are sent by default, but can be disabled or require users to opt-in. Please see the notification configuration and adding a project for more details.
When committed change notifications are configured for opt-in, you need to copy the configuration's special depot path to the Reviews: field in your user spec within Helix Server. Once you have done so, Swarm can send you committed change notifications for any change that matches a depot path specified in the Reviews: field.
Begin editing your user spec:
$ p4 user
Reviews: field to include the special depot path, plus any other paths you want to receive notifications for.Reviews: field to include the special depot path, plus any other paths you want to receive notifications for.By default, notifications are sent when a review is started, but can be disabled for a project, group, or user.
If a user or group is added as a reviewer when a new review is created, the reviewer will be notified that the review has been started. This initial notification cannot be muted.
Moderators and moderator groups are associated with specific project branches. Moderators receive notifications for reviews and commits against the branches they are associated with.
Groups can be members of a project, moderators of a project branch, and reviewers of a review. The notifications that group members receive will depend on, the role the group has and the group notification settings that are configured for that group. Notifications received by group members also depend on whether the group has a group mailing list enabled, in this case additional notification settings are available. See Group mailing list enabled below for details.
Group members can be notified when a member of the group starts a review. Group members can also be notified when a change is committed by, or on behalf of, a changelist owner who is also a member of the group. These two notifications can be individually selected as required. See Add a group for details.
Notifications are sent to the group members individual email addresses.
Group members can be notified when a member of the group starts a review. Group members can also be notified when a change is committed by, or on behalf of, a changelist owner who is also a member of the group. These two notifications can be individually selected as required.
Additional notifications are available if the group mailing list address is enabled. See Add a group for details.
Notifications are sent to the group email address.
By default, notifications for events in a review are sent to all reviewers. Reviewers can disable notifications during a review to avoid further email notifications. Once notifications are disabled for a reviewer, they can be re-enabled when they are specifically @mentioned; reviewers can disable notifications again after they have been re-enabled. See Disable notifications for details.
By default, notifications are not sent to comment authors, but Swarm can be configured to send notifications of comments to comment authors. See notify_self for details.
By default, notifications are sent when:
      |
|