What's new in 2017.3

This section provides a summary of the notable changes in Swarm for the 2017.3 release. Full details are available in the distribution's RELNOTES.txt file.

Be aware:

Upgrade index on upgrade to improve performance
The upgrade process has changed. The Swarm index must be upgraded to ensure that the Swarm review history is displayed in the correct order. This step is only required the first time you upgrade your Swarm system to 2017.3 or later. Subsequent Swarm upgrades do not require the index to be upgraded. If this is a new Swarm installation, the index does not need to be upgraded.
See Upgrade index for details

Major new functionality

Groups as reviewers
Swarm groups can now be set as reviewers for reviews. A reviewer group can be set as an optional reviewer, a required reviewer (all votes required), or a required reviewer (one vote required).
See Reviewers for details.
Groups as project moderators
Swarm groups can now be set as moderators for project branches. When a group is specified as a moderator, all of the members of that group have the same moderator privileges for that project branch as if they were added individually.
See Add a project for details.
Group mailing list and additional group notifications
Swarm groups can now have a group mailing list email address, notification emails are sent to the group email address rather than the group members individual email addresses. When group mailing list is enabled for a group, additional notifications can be set for the group.
See Add a group for details.
Group avatars
Swarm groups now have avatars, these can be customized in the same way as a user avatar. The group avatar is used in reviews when the group is set as a reviewer, in projects when the group is a project member, and in projects when the group is a moderator of a project branch.
See Avatars for details.
Group @@mention
You can now use @@mention for groups. When a user @@mentions a group in a comment, a list of groups is provided via a dropdown menu. This helps ensure that the right group of people are notified.
Using @@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.
See @mention for details.
Security Enhanced Linux on CentOS 7
Swarm now supports SELinux on CentOS 7. SELinux is an advanced access control mechanism that improves security for Linux distributions.
See Security-enhanced Linux (SELinux) for details.
Review sort order and user filter
You can now choose to sort reviews by review Created or Last Activity from a dropdown menu. The User filter dropdown now has a new filter called Reviews I've Authored Or Am Participating in.
See Review queues for details.
API updated to version 7
A number of new endpoints have been added to the API, and it has been updated to v7.
See Swarm API for details.

Minor new functionality

User notification options updated
The user notification settings are now ordered by user role.
See Settings for details.
User email shown on user profile sidebar
The user email address is now shown in the sidebar below the user avatar.
See Users for details
Group email shown on group sidebar
If a group has a group mailing list, the group mailing list email address is now shown in the sidebar below the group avatar.
See Viewing a group for details
Bell icons removed from groups page
The bell notification icons have now been removed from the groups page.
Fixed review state filters in IE11
Review state filters were not working in Microsoft Internet Explorer 11, they have now been fixed

Known limitations

Access Control
Swarm maintains a variety of information in the Helix Versioning Engine's keys facility. By default, users with list-level privileges can read these keys, which can include comments that contain excerpts of code they may not normally have access to.
The Helix Versioning Engine, version 2013.1/659207 or higher, has a configuration setting to require admin-level privileges for access to read and write keys. See Hiding Swarm storage from regular users.
Task Stream Reviews
Pre-commit reviews in a task stream are not yet supported.