Released on January 12, 2023
Enhancements
- Added full support for Rancher 2 auto-provisioning.
- If Rancher 2.6 is available in your toolchain, all users which have the RANCHER2 tool assigned receive the global permission User-Base on Rancher. User-Base users have login-access only. But they can be added to clusters and namespaces.
- All users who have at least one project admin role get the global permission Standard User on Rancher. These users can create new clusters and use them. Standard users can also assign other users access permissions to their clusters.
- The portal now automatically maintains a group on Jira named project-admins which contains all users which have at least one project admin role. This group will be used to manage the access permissions for the Jira Roadmap Feature of the Jira Data Center edition. More about this will be made public in a separate posting.
- The view and edit project pages have been unified. Therefore, the actions View and Edit have been removed from the More menu. Simply click on the project key of a project to view it. If you want to change any data, tick the checkbox Edit Details. This is only available if you have the admin permissions on the project and the project you want to edit is in ACTIVE state at the moment.
When a new user is created or an existing user is changed and the new portal role or the old portal role is admin, all other admins are informed by mail who did the change and which user was made a portal admin or lost the role.
- All pages have been improved concerning accessibility.
- Required fields now have an additional * symbol, so you know that you have to enter something in any case.
- Status and error messages are now correctly marked for screen readers.
- Error messages related to input fields have been moved to the label to support screen readers.
- Detail dialogs of projects, users, technical users, organizations and usage terms can now be opened using CTRL and left mouse button in a new browser window. This allows for fast processing of multiple entries.
- When multiple browser tabs are used to open the different tools, it was hard to distinguish which tab is for which tools. Therefore, our favicons as known from https://geschaeftskunden.telekom.de/digitale-loesungen/infrastructure-as-a-service/devops-as-a-service#leistungen are now used for Jira, Confluence, Bitbucket and gitlab. Since your browser caches favicons for a longer time, it's possible that you still see the old favicon. If this is the case, try holding the shift key while you press the reload button in the browser. That will force the reload of the favicon. Icons for the remaining tools will be added in the future.
Improvements
- The notification mails that users receive about changes in their licence assignments now contain a list of tools that is sorted like in the portal.
Bugfixes
- Changes in the description field of a project were not set on Bitbucket if the name of the project was not changed, too.
- Small bugfixes concerning auto-provisioning of Rancher 2 and SonarQube.
Known Issues
- 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 will automatically repair it for you. Problem is fixed for customers which have Rancher v2.6 in their toolchain as it happens only with Rancher 1.6.