GForge 25.0 Released!
The GForge Group team is happy to announce the release of GForge 25.0! This is primarily a feature release, though it includes a number of bug fixes and infrastructure updates.
Key Highlights in 25.0
- Core System
- Added support for Microsoft SSO (oAuth). We already supported this for SaaS, this feature is for on-prem customers who want to configure their GForge instance to only use Microsoft (and not others like Google, etc)
- Continued work on the migration from AngularJS ot Angular
- Fixed an issue with Postfix not restarting cleanly during GForge restarts.
- Site Admin
- Site Admins now receive email and in-app notifications when a user account is locked, enabling more proactive support.
- Added configuration options related to authentication:
- Password aging rules
- Password reuse rules/restrictions
- Notification preferences on account lockouts
- Introduced a new cron job administration page allowing Site Admins to view and manage the status of all GForge cron jobs.
- Fixed a bug where the User Administration page incorrectly displayed groups.
- Version Control
- Git Blame is now available while browsing Git repositories.
- Fixed a bug where switching from Subversion to Git still allowed commits to the SVN repository.
- Corrected the example provided for using Subversion over SSH.
- Tickets
- Mass Update now allows the addition of tags to multiple tickets (note: tag removal is not supported yet)
- The Planning Board now includes direct links to it’s underlying data sources.
- Fixed a bug where saved queries spanning multiple sprints would fail to load properly.
- Improved performance when displaying tickets with high activity (e.g. follow-ups, commits).
The 25.0 ChangeLog details all the changes made in this release.