Archive
Last modified by DOaaS Operator on 2025/11/19 16:02
Blog - posts for February 2026
Feb 16 2026
Feb 16, 2026,
DevOps Portal 2.2.2
Improvements
- Customers can now issue a service request to have a certain set of tools preselected, when they create a new project or user.
- Updated Angular to fix some vulnerabilities.
Bugfixes
- When a project was saved, the project lead in Jira was set to sdcloud-admin since the previous version 2.2.1. This is fixed now, so if any user is set as the project lead, it will be kept.
- In some rare cases it could happen that Portal Technical Users were not listed on the Technical Users page. This is fixed now, so that refreshing the page is no longer required. Please note that Portal Technical User for Portal API access are only available, if you use a service request to enable the feature on your instance.
- In some rare cases it could happen that the Log-in button in the Re-Authenticate dialog was not clickable.
Feb 12 2026
Feb 12, 2026,
DevOps Portal 2.2.1
Improvements
- More columns were added to the License page for Portal Admins now showing more details about the license consumption.
- The Helm Charts link in the Habor tile of the dashboard is now linked to the new PROJECTKEY-helm project in Harbor which stores OCI Repositories.
- The date picker on the Audits page is now fully localized and will use the date format of the selected locale.
- Searching the audit log for patterns now works for the whole time period selected in the date picker.
- Customers can now order retention times for the audit log which are longer than the default of 90 days.
- When a user is deleted in the DevOps Portal, it needs to be deleted in all the tools. In Jira it can happen that a user is still a reporter or assignee of an issue. The user could be also listed as component lead in a project. In these cases, the user cannot be deleted. In the past these users were just set to inactive. This is a problem concerning data privacy. Therefore these users are now anonymized.
- In Harbor users can copy a CLI secret from their User Profile page to use it with docker and helm commands. It's now enforced that this CLI secret doesn't work when a user is locked. Since all roles are removed from locked users, the situation before was seen as secure enough, but now it's even better. When a user is unlocked, he or she needs to login at least once to Harbor to make the CLI secret work again.
- Portal Admins can force activating a created user on the users page. This action failed when the invitation link, which was sent to the new user, was expired. This has been changed, so that a created user can be forced to active at any time. In general, it's recommended to use this feature only for exceptions, as it skips the verification of the email.
- The DevOps Portal database was upgraded to PostgreSQL v16.
- The Keycloak database was upgraded to PostgreSQL v16.
Bugfixes
- For some notification emails it could happen that the saved locale of the user was not used. This could lead to an English email sent to somebody who had selected German before. This is fixed now for all emails.
- In some rare cases it could happen that the Log-in button in the Re-Authenticate dialog was not clickable.
- Locking and Deletion of technical users are now correctly recorded as TECH_USER_LIFECYCLE_CHANGEs instead of TECH_USER_CHANGEs in the audit log.
- When deleting retired projects, the total and remaining count at the top was not immediately updated, just after a page refresh. This is fixed now.
- A bug introduced in the previous version did overwrite Jira schemes with the ones configured on the project details page. This is now fixed, so that custom schemes can be set in Jira only and will be kept. For notification schemes the behavior is correct, since these schemes can be changed any time in the portal. It was only a problem with the other schemes that can be only set during project creation.