Archive
Last modified by DOaaS Operator on 2025/11/19 16:02
Blog - posts for April 2026
Apr 01 2026
Apr 1, 2026,
DevOps Portal 2.2.4
Enhancements
- The function Retire Project has been renamed to Close Project. In the German translation this term was already used before. In addition, the behavior of the feature has changed. Both functions Close Project and Delete Project are only available to Portal Admins as before. It's also unchanged that a project needs to be closed before it can be deleted later. When closing a project, the Portal asks for a confirmation first, which includes a warning that all Role Assignments for Users and Tech Users will be lost and cannot be recovered. Like for deletion, the project name needs to be entered for the confirmation. When the DevOps Portal sets the status to Closed, all role assignments of Users and Tech Users are deleted, too. All role removals are recorded in the audit log, exactly like if the actor had removed the roles manually. Only Portal Admins can see closed projects, because they don't need a role in projects to see them. Portal Admins cannot add roles again without Reactivating the project first.
- The in-memory cache of the DevOps Portal was replaced by a distributed memory cache. This will allow to scale the Portal in the future, i.e. run multiple instances at the same time. In addition, this will enable down-time free updates in the near future by running an old and a new version of the Portal in parallel for a short period of time.
Improvements
- Customers can now raise service requests, if they want to have a tool removed from an existing project. Please double check which project and tool, since this can lead to unrecoverable data loss.
- Added more visual indications when an invalid time period is selected on the Audits page.