Significant performance improvement in determining if the user has a specific permission. For a view with 100's of jobs and a user with 10's of external groups this has been reported to reduce page rendering time from over 30s to sub-second
Simple option to create a typical set of groups and roles when starting out.
CLI command to list or set group membership.
On some versions of Jenkins, after a reload, changes to groups of Nodes were not being persisted until Jenkins was restarted
If you don't have permission to configure a group that you have created, bring you to the manage screen rather than the configure screen
Missing permission check on group list page.