Skip to Content

Wiki source code of Release Notes 1.2

Last modified by DevOps-as-a-Service Operator on 2025/02/05 11:33
Show last authors
1 == Release 1.2.9 / 🗓 14 Dec 2022 ==
2
3 === Enhancements ===
4
5 * The previous version 1.2.8 was released just for some customers, therefore make sure to also read its release notes. The most important feature that was added is full support for [[doc:SonarQube.WebHome]]. Please follow the link to get a complete overview about our [[doc:SonarQube.WebHome]] offering, how it's integrated into the portal and how to use it.
6 * Whether 2FA (Two-factor authenthication) is enabled or not for a user can now be directly seen in the status column of the users list. Sorting by status works as expected. You can also use the search box to search for any status like e.g. only "2FA" or "LOCKED 2FA", etc.
7 [[image:attach:image2022-12-8_18-6-48.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="160" width="100"]]
8
9 === Bugfixes ===
10
11 * When a user is locked or saved after editing it can happen that the portal lists a pending synchronization, if the user cannot be found on SonarQube because he or she never got the tool assigned. This warning is harmless and was fixed.
12 * For customers which have their own support email address configured in the portal footer there is the following issue: permanent pending syncs are sent as a warning email to this address. This was not intended and was fixed. Warnings are processed by the Service Desk DevOps-as-a-Service.
13
14 === Known Issues ===
15
16 * (% style="color:#172b4d" %)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.
17
18 == Release 1.2.8 / 🗓 01 Dec 2022 ==
19
20 Only released to SonarQube pilot customers.
21
22 === Enhancements ===
23
24 * Now offering [[SonarQube>>url:https://www.sonarqube.org/||shape="rect"]] as an additional optional tool with full integration into DevOps-as-a-Service. The latest version of SonarQube - at the moment of writing - v9.7.1 is offered. Project roles are fully managed by the DevOps portal. Please note that SonarQube projects are different to projects in the DevOps portal and the existing tools. In Bitbucket a project can have multiple git repositories which all have their own build pipelines in Jenkins. SonarQube projects contain the scan results of just one git repository. They are created on-the-fly using the [[doc:Jenkins.Jenkins Shared Library.WebHome]] when a scan is executed but the projects is not yet existing. To activate SonarQube it's required to save every project in the DevOps portal first. After this step SonarQube can be added to individual users just by editing them. More information about SonarQube and its integration into the DevOps toolchain will be published seperately.
25 * Auto-provisioning for project roles in Rancher 2.6  was added.
26
27 === Improvements ===
28
29 * Since LDAP cannot properly handle organization names which differ just concerning uppercase and lowercase letters, the check for unique organization names is now case-insensitive.
30 * Improved testing of auto-provisioning for Confluence, Bitbucket and Keycloak.
31 * Updated to more recent nodejs and npm versions.
32 * Improved JavaScript code.
33 * Moved more internal testing to new Rancher 2 RKE clusters.
34
35 === Bugfixes ===
36
37 * Improved layout of bubble help pop-ups.
38
39 === Known Issues ===
40
41 * If a user is locked or saved after editing it can happen that the portal lists a pending synchronization if the user cannot be found on SonarQube because he or she never got the tool assigned. This warning is harmless and will be fixed in the next release.
42 * For customers which have their own support email address configured in the portal footer there is the following issue: permanent pending syncs are sent as a warning email to this address. This was not intended and will be fixed in the next release.
43 * (% style="color:#172b4d" %)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.
44
45 == Release 1.2.7 / 🗓 02 Nov 2022 ==
46
47 === Enhancements ===
48
49 * Unified the view and edit dialog for Technical Users like it was already done for Users. Now it's also possible to change the description of a Technical User without changing its password.
50 * Unified the view and edit dialog for Organizations like it was already done for Users.
51
52 === Improvements ===
53
54 * On the Organizations page the displayed count for visible and total number of Organizations was added, as well as a bubble help which desribes the purpose of Organizations.
55
56 === Bugfixes ===
57
58 * When a user record was edited, it could happen that pending syncs complained about different upper and lower cases in email addresses in the Portal versus Jira and Jira Service Management.
59
60 === Known Issues ===
61
62 * (% style="color:#172b4d" %)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.
63
64 == Release 1.2.6 / 🗓 19 Oct 2022 ==
65
66 === Enhancements ===
67
68 * **Two Factor Authentication (2FA) **can now be activated or deactivated for each user directly in the portal. To change it go to the users details page and set or unset the checkbox.
69 [[image:attach:image2022-10-20_16-56-34.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="60" width="284"]]
70 2FA improves the security of your DevOps toolchain since users will be prompted for an additional one-time password (OTP) in addition to their normal credentials during the login. Users with 2FA enabled will need to use an application that implements the **Time-Based One-Time Password Algorithm (TOTP) **as defined in [[RFC 6238>>url:https://www.rfc-editor.org/rfc/rfc6238||shape="rect"]]. Usually a mobile application like e.g. [[Google Authenticator>>url:https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=de&gl=US||shape="rect"]] or [[Microsoft Authenticator for Android>>url:https://play.google.com/store/apps/details?id=com.azure.authenticator&hl=de&gl=US||shape="rect"]]/[[Microsoft Authenticator for iOS>>url:https://apps.apple.com/de/app/microsoft-authenticator/id983156458||shape="rect"]] is used for that. If a user loses it's mobile phone simply disable 2FA, save the user details and afterwards enable 2FA again. This will make sure that the association with the authenticator app is deleted, so that the user can connect a new app. In the Create User dialog 2FA defaults to true.
71 * (((
72 SSO Realm Names have been changed from "DevOps as a Service" to the domain name of your instance, e.g. [[CUSTOMER.devops.t-systems-service.com>>url:http://CUSTOMER.devops.t-systems-service.com||shape="rect"]] or [[CUSTOMER.devops.t-systems.net>>url:http://CUSTOMER.devops.t-systems.net||shape="rect"]]. This will avoid duplicate entries in mobile apps like Google Authenticator and allows you to easily distinguish between multiple instances if necessary.
73 )))
74 * A column was added to the list of organizations which shows when the organizations were created.
75
76 === Improvements ===
77
78 * To improve the support for your users we are now offering the possibility to change the contact link in the portal footer. Please create a service request to have it changed.
79 * Automated notification emails sent by the DevOps portal will no longer mention the T-Systems DevOps support email address, but instead link to your DevOps portal. This will ensure that users with questions e.g. about role changes will be able to contact the right people.
80 * To avoid problems in some of the DevOps tools the length of the firstname and lastname for users as well as the length of organization names was limited to 64 characters.
81 * The description field for technical users was limited to 1024 characters.
82 * The term Global Role was renamed to Portal Role to more clearly specify to what ADMIN and USER refer to.
83 * Activated date and unlocked date are now only viewable by portal ADMINs or for the own user to keep this information more private.
84
85 === Bugfixes ===
86
87 * A bug was fixed which could prevent organization name changes in some cases.
88 * Work-around for Jira problem: the auto-provision code for Jira can now sucessfully process Jira API replies which in some cases can return already deleted users.
89 * For locked users the activation timestamp was not shown on the user details page.
90 * Project counter was not updated immediately for users or technical users when they were assigned or unassigned from a project.
91 * Fixed a text problem on the metrics page.
92
93 === Known Issues ===
94
95 * (% style="color:#172b4d" %)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. Will be fixed when the Rancher in customer's toolchain is updated from v1.6 to v2.x.
96
97 == Release 1.2.5 / ​​​​​​​🗓 03 Aug 2022 ==
98
99 === Bugfixes and Improvements ===
100
101 * The DevOps Portal application was upgraded from JDK 11 to JDK 17.
102 * The font used in the single-sign-on (SSO) page was enlarged for better readability.
103 * Timestamps for the activation of an user as well as for the last unlock operation invoked on the user are now recorded. The timestamps are displayed on the users details page.
104 * On pages with data entry fields the first field is now automatically focused so that you can type immediately without the need to select the field before.
105 * The Portal will now accept emails up to an length of 64 characters.
106 * Added more automated test cases to the development process.
107 * Preparations for developing and operating the portal on Kubernetes only.
108
109 === Known Issues ===
110
111 * (% style="color:#172b4d" %)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. Will be fixed when the Rancher in customer's toolchain is updated from v1.6 to v2.x.
112
113 == Release 1.2.4 /​​​​​​​ 🗓 06 Jul 2022 ==
114
115 === Enhancements ===
116
117 * (((
118 **Bulk Role Management for Technical Users.** The role management for technical users is now integrated in the Technical Users page like it was done for users in the previous release. This new feature allows you to assign or unassign project roles to multiple technical users in just one action. It's also perfect to get an overview about already assigned roles in a specific project since it really shows all available information about the affected technical users. Usage is very simple: select the project in the combo box and see the users sorted by project role below. Two dashes ("–") are used as a symbol for no role. Global or project admins can change the role of technical users by selecting them with the check boxes on the left-hand side and then use the //Assign //button to assign the desired role to these technical users. To remove roles simply select "–" as new role. The selection in the combo boxes project and new role are persisted accross sessions.
119
120 {{info title="Note for global admins"}}
121 In the past it was enough to create a new technical user when a project admin without global permission asked for it. Now the security has been increased and all project admins will only see technical users which have a role in one of their projects. Therefore after creating the technical user assign a role like e.g. VIEWER matching the project of the project admin. This will make the technical user visible for the project admin and he can change the role appropriately, add more roles relating to other projects etc.
122 {{/info}}
123 )))
124 * The view and edit user pages have been unified. Therefore the actions View and Edit have been removed from the //More //menu. Simply click on the last name of a user to view him. If you want to change any data tick the checkbox //Edit Details//. This is only available if you have the global admin role and the user you want to edit should not be LOCKED at the moment. To be able to edit a LOCKED user first UNLOCK him.
125 * Users now get an email if their account was modified on the above mentioned edit page.
126 * For ordinary users the amount of used and remaining licences is no longer shown anywhere.
127 * Users which are not in the default organisation can see only other users in the same organisation or users which are members of a common project. This also works when viewing the details of a user. Confidential information like e.g. tool assignments or creation date are not displayed.
128 * To save one click, the login form is now immediately shown when navigating to the portal and there's no active session.
129 * The queue handling, which in the background manages the auto provisioning of the tools, was massively improved to avoid any deadlocks concerning conflicting changes fired at high pace.
130 * Pending syncs are now more readable.
131
132 === Bugfixes and Improvements ===
133
134 * The assignment and unassignment of Jira Service Management licences for users and technical users was broken and is now fixed.
135 * The item count was not displayed for standard users on User page.
136 * Resync roles has been forbidden for retired projects to prepare for the full implementation of project retirement. To resync roles for a retired project simply reactivate it.
137 * Some improvements for narrow screens. Improved widget reflow.
138 * Burger menu is now closed after selecting the //User Profile //menu item.
139 * Upgraded version of Keycloak used for single-sign-on.
140 * Updated version of database server instances.
141 * Adapted auto-provisioning to changed APIs at Jenkins.
142 * Improved automated testing for an even better QA concerning UI and end-to-end behavior.
143
144 === Known Issues ===
145
146 * (% style="color:#172b4d" %)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. Will be fixed when the Rancher in customer's toolchain is updated from v1.6 to v2.x.
147
148 == Release 1.2.3 / ​​​​​​​🗓 05 May 2022 ==
149
150 === Bugfixes and Improvements ===
151
152 * Fixed no longer working Jenkins auto-provisioning by switching authentication to API tokens.
153 * Selection checkboxes for entries on the Users page are no longer shown if logged in user is not allowed to use the role assignment for the currenty selected project.
154
155 === Known Issues ===
156
157 * (% style="color:#172b4d" %)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. Will be fixed when the Rancher in customer's toolchain is updated from v1.6 to v2.x.
158
159 == Release 1.2.2 / ​​​​​​​🗓 28 Apr 2022 ==
160
161 === Enhancements ===
162
163 * **Bulk Role Management for Users.** The role management is now integrated in the Users page. This great new feature allows you to assign or unassign project roles to multiple users in just one action. It's also perfect to get an overview about already assigned roles in a specific project since it really shows all available information about the affected users. Usage is very simple: select the project in the combo box and see the users sorted by project role below. Two dashes ("–") are used as a symbol for no role. Global or project admins can change the role of users by selecting them with the check boxes on the left-hand side and then use the //Assign //button to assign the desired role to these users. To remove roles simply select "–" as new role. The selection in the combo boxes project and new role are persisted accross sessions.
164 * All projects now automatically get a [[RAW repository>>url:https://help.sonatype.com/repomanager3/nexus-repository-administration/formats/raw-repositories||shape="rect"]] on Nexus (if available) with the name //<Project Key>//-raw. Basically a RAW repo is like a static HTTP server. You can use it to publish HTML pages, e.g. JavaDocs or any other static files which are not covered by the programming language specific repo formats. RAW repos have also been added to all existing projects.
165 * On the Technical Users page the number of assigned roles for each tech user is now displayed
166 * On the Organizations page the number of members in each organization is now displayed
167 * Improved accessability of the portal to allow better usage by users with disabilities. This includes e.g. correct formatting of pages with very high zoom factors, screen reader support, high contrast mode support, alternatives to just using colors for information transport, etc.
168 * Tables now have only one link per row which is used to open the item in view mode
169 * Portal now perfectly usable on mobile devices with smaller screens
170 * Page titles for e.g. browser tab names now include the portal name which improves navigation in a crowded browser
171 * On the Projects page users now only get deep links for tools which they can really access. Tools for which a user doesn't have a licence assigned are no longer listed. Global admins who can see all projects will get just tool names without links for each project where they don't have currently a role assigned.
172 * Updated Portal to new versions of the underlying technology like JHipster and Angular.
173
174 === Bugfixes and Improvements ===
175
176 * Technical users for Jira cannot be completely deleted on Jira when they have issues assigned. Instead they will be set to inactive in Jira. If you want to have a tech user completeley delete in Jira make sure to unassing all issues before deleting the user in the portal.
177 * Improved robustness of auto provisioning when one or multiple tools are not available during auto provisioning process
178 * Searching for special characters like ! or ? in the status field of users works again
179 * Creating Tech Users for Jira Service Management works again
180 * Fixed some problems caused by the renaming of Jira ServiceDesk to Jira Service Management.
181 * Adding more code for upcoming Rancher 2 support
182 * Improved menu bar for narrow screens
183 * Project list on User Detail pages is now alphabetically sorted
184 * The validity of links in user activation mails and password reset mails is now always correctly specified in localized format, also for non default time periods.
185 * Simplified readability of License Usage page
186 * Numbers in tables are now right-aligned for better readability
187 * Now avoiding flickering due to error messages like "Password is too short" while typing in a new password
188 * Updated data base version
189
190 === Known Issues ===
191
192 * (% style="color:#172b4d" %)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.
193
194 == Release 1.2.1 / ​​​​​​​🗓 02 Feb 2022 ==
195
196 === Enhancements ===
197
198 * The projects page now shows the amount of members of a project. Suitable to learn about the size of a project. Old projects with 0 members are certainly good candidates for a retirement.
199 * Issue-type schemes in Jira are now automatically deleted when the matching project is deleted on the portal.
200 * Prepared the UI at multiple places for the upcoming Bulk Role Management feature.
201 * Prepared LDAP structure for the upcoming Rancher 2.x auto-provisioning support.
202 * Adapted security measures to the upcoming hosting based on Rancher 2 and Kubernetes.
203
204 === Bugfixes and Improvements ===
205
206 * Streamlined the different pages so that similar things are solved similar.
207 * The top magenta header is now better aligned and uses less space.
208 * Jira ServiceDesk was renamed to Jira Service Management to reflect the change of the product name of Atlassian. The short version is ServiceMgmt.
209 * Changes on the Terms & Conditions are now logged to the audit log.
210 * Audit log now shows real usernames instead of UUIDs for logins.
211 * Searching for translated columns is now working using the currently selected locale.
212 * Projects could not be created if a Rancher environment with the same prefix had been already manually created.
213 * Caching problem after version update is now solved. Reload message will no longer appear starting with 1.2.2.
214 * Improved automated testing during development.
215
216 === Known Issues ===
217
218 * (% style="color:#172b4d" %)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.
219
220 == Release 1.2.0 / ​​​​​​​🗓 09 Dec 2021 ==
221
222 === Enhancements ===
223
224 * When the portal creates a new project on Jira an associated Agile Scrum Board is automatically created, too. In the past users could not modify the configuration of this default board. Now if a new ADMIN role is assigned the user will be automatically added to the list of administrators of the board. This allows project admins to configure the board like they wish. One of the most useful possibilites is to add new columns and statuses. By doing this, new kinds of workflows can be created on the fly for the project. See [[doc:Jira.WebHome||anchor="ManageBoards"]] for complete instructions. To put all existing ADMIN users of a project to the list of board administrators simply invoke //Resync Roles// using the More menu on the Projects page of the portal. This feature is available both to Project Admins as well as to Global Admins. Further changes to the roles will automatically sync with the list of board administrators.
225 * A //User Profile// page was added to the Account menu which shows information about the own user account.
226 * (% style="color:#172b4d" %)Added search filter for Technical Users like already available for Users.
227
228 === Bugfixes and Improvements ===
229
230 * Searching now also considers the created timestamp of Projects and Users.
231 * For Projects, Users and Technical Users the page header now shows the amount of displayed items when the search is used, but also shows always the total amount of items.
232 * The amount of used licenses is now also in detail calculated for Open Source tools. See //Administration / Limits// in the portal for more information.
233 * Massively improved the German translation of the portal.
234 * The validity of invitation links in invitation emails is now by default 1 week. You still can send out new invitations by using the //Reinvite //menu item in the More menu of the affected user.
235 * The footer is now always displayed at the very bottom of the page and displays the complete content also on very narrow windows.
236 * Due to data privacy issues the created timestamp and list of assigned tools for other users than themselves can no longer be seen by ordinary users. It's still available for Global Admins.
237 * Solved problem with removing user roles in Gitlab which could be triggered only in some special conditions.
238
239 === Known Issues ===
240
241 * (% style="color:#172b4d" %)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.
242
243
© 2018-2025 T-Systems International GmbH