DevOps Portal 1.9.2

Last modified by Boris Folgmann on 2025/07/09 16:05

New feature

Enhancements

  • Prepared support for the tool Dependency Track which will allow automated SBOM analysis together with Jenkins.
  • AI Operator is now automatically connected to Jira using a read-only technical user. To enable the feature for existing projects with AI Operator and Jira a Project Admin simply needs to edit and save the project. This adds more functionality to AI Operator since it can now read all your Jira issues in addition to Confluence pages.
  • Added RestAPI for user management. Portal Admins can now use the API to create, update or delete users. All other status transitions are also supported like e.g. lock and unlock. See Swagger screenshot below:
    1752075376168-983.png

Improvements

  • Since the DevOps Portal sometimes requires technical user accounts with assigned licenses to connect one tool with another, the Create Project page has been improved to make this more transparent. Lets's say you have selected some tools for a new project. Now you also select Jenkins. Then some info messages will appear and show you which tool will have to contribute 1 or 2 licenses for a successful connection with Jenkins. The following screenshot shows a sample tool selection with and without Jenkins.
    1752060436721-347.png  →  1752060455874-412.png
  • The Workspace read permission in Jenkins is now also granted to DEVELOPERs, not only ADMINs and MASTERs. This improves self-service for DEVELOPERs for troubleshooting build failures.
  • The Health Checks page for Portal Admins was removed. Due to technology changes, it did no longer offer any added value. Instead, use the dashboards which are automatically available for all users in the Main Org of Grafana to see much more metrics and statuses.
  • Changes of the 2FA setting of a user are now more clearly logged in the Audit Log.
  • The instructions a new user sees in emails or in the web browser during onboarding are now different depending on if 2FA was enabled or not. This makes it easier to understand and follow the process.

Bugfixes

  • When the DevOps-as-a-Service session timed out after 5 hours of inactivity, it could happen that a still opened DevOps Portal was not correctly redirecting the user to the login page, but instead was showing an error. This was a problem caused by the new JWT implementation introduced in DevOps Portal 1.9.1 and has been fixed.
  • Some links in the footer were not correctly adapted when the user changed his or her favorite language.