Release Notes 1.1

Last modified by DevOps-as-a-Service Operator on 2025/02/05 11:33

Release 1.1.5 / 🗓 17 Nov 2021

Improved validation of project name to avoid special characters which can cause trouble in one of the DevOps tools.
Improved code quality
Updated Database Server version
Technical users couldn't be created on nexus if they shared a prefix with an existing user.
Remaining licences were no properly checked when technical users were created.
Fixed display problem in Firefox for narrow windows.

User update/lock action can be stuck when the user was assigned to another organization after the user's first project role assignment. The ops team can automatically repair it for you.

Users with ADMIN access on project level can now trigger Resync Roles for individual projects. Since project ADMINs can change permissions inside projects in the tools, this is a comfortable feature to ensure that all roles are reset to exactly what is defined in the portal. Missing roles will be added and incorrect roles or permissions will be fixed. Please note that the permissions of users which don't have a role in the portal will not be touched in the tools. To get rid of them, it's required to manually remove them. Of course, this would be only necessary if permissions have been previously manually modified in the tools.
It's now possible to completely remove tools from the portal, project and users. This new feature is required to allow the exchange of individual tools in the future.

User update/lock action can be stuck when the user was assigned to another organization after the user's first project role assignment. The ops team can automatically repair it for you.

Creating a new user with an email address (e.g. company.com) that is a prefix of the mail address of an existing user (e.g. company.com.br) is now possible.
Roles in Jira and Confluence are now explicitly removed for deleted users.
Data base update

User update/lock action can be stuck when the user was assigned to another organization after the user's first project role assignment.
Pending roles are not deleted from the job_queue when the project is deleted.
Under specific circumstances, one pending user lock action can remove later added roles in the tools.

When a single tool is disabled for a user, for commercial tools the license is removed and for Open Source tools his roles are removed. The same is true for all tools when a user is LOCKED. In the past, when the tool was enabled again or the user was UNLOCKED licences were assigned, but roles in OpenSource tools were not added. This is now fixed. The user will receive all his roles for all affected projects in the Open Source tools.
New IAM versions should not require any browser cache flushes
Login screen improved for smaller displays
Automated testing for our SSO-enabled environments
Bugfixes concerning the new gitlab integration that is already in use by a pilot customer
Smaller bugfixes and improvements

Pending Roles are not deleted from the job_queue when the project is deleted
Under specific circumstances, one pending user lock action can remove later added roles in the tools

Jenkins now supports Single-Sign-On (SSO) and is integrated into the existing SSO domain.

Customers can make a change request to have their own helpdesk email addresses added to mails that are automatically sent by the portal, like e.g. invitations, role changes, etc.
Deep link to project's repo in Nexus had to be fixed in the portal due to changes on Nexus side.
Bugfixes concerning the new gitlab integration that is already in use by a pilot customer
Smaller bugfixes and improvements

Pending Roles are not deleted from the job_queue when the project is deleted
Under specific circumstances, one pending user lock action can remove later added roles in the tools
Sometimes the browser cache must be deleted at client side to fix errors after changes in the DevOps-Portal
changing the name of an existing organization can lead to limitations or login difficulties for existing and new users

The DevOps-Portal now supports Single-Sign-On (SSO) and is integrated into the existing SSO domain

Pending Roles are not deleted from the job_queue when the project is deleted
Under specific circumstances, one pending user lock action can remove later added roles in the tools
Sometimes the browser cache must be deleted at client side to fix errors after changes in the DevOps-Portal