2.2.0

Currently, when creating a new status report, only the creator and the time of creation are saved as meta information. Therefore, a comment field was added to the status report model, which will allow users to add a comment or description to their status report. Note: At the moment, the comment field has only been added to the status report model. It is not yet visible as a column in the grid.

This feature relates to the list of all projects, which can be accessed by navigating to   > Configuration > Projects. Specifically, it relates to situations when users click on  Edit mode in the lower left corner of the grid. Now users are able to double-click on the project image and upload a new image or remove an existing image.

This feature relates to the list of all projects, which can be accessed by navigating to   > Configuration > Projects. This list now includes an Owner column. When creating a new project, the user who creates the project is automatically assigned as its owner. The owner can be thought of as a “super user” for that specific project, i.e. the owner has full permission to configure the project regardless of their global role or assigned permissions.

Note: The owner is automatically assigned when creating a new project. No owner is automatically assigned to existing projects, i.e. the Owner column is empty.

The update, delete, publish and derive actions on a status report policy now check whether the user is a super user. Super users now have the right to perform these actions.

This feature relates to the list of all projects, which can be accessed by navigating to   > Configuration > Projects. Now when users click on  New, the grid becomes editable and a new row is added to the top. In this new row, users enter a name, description and image for the new project.

This improvement relates to the test grid in  Result. Users can now activate “edit mode” and then edit the cells just like they would an Excel spreadsheet. The basic workflow is as follows:

1. Click on  Edit mode in the lower left corner of the test grid.
2. Double-click on an editable cell in the grid, e.g. a cell that does not have a striped background.
3. Edit the cell as necessary. Continue editing any other cells the same way.
4. Click on  Save when you are finished.

Note: The preset configuration determines which columns are editable. Editable columns have the attribute writeable with the value true.

This feature relates to the Set as project status function. Specifically, it relates to the Debug test case matching area, where users can see e.g. why a specific test did or did not match a specific test case. The drop-down list now displays test cases from whichever project was selected in the Select status target window. For example:

• Select status target: The project “Yaris” is selected in this window.
• Debug test case matching: The drop-down list will display test cases for the project “Yaris”.

The menu can be accessed by navigating to   > Configuration > Operational > Preset cache monitor. Here admins see a list of all available presets and the status of their columns and scenarios. For each preset, the number of computed (cached) objects and the number of total objects are displayed side-by-side. A color indicator helps users read the data quickly. Green numbers indicate that everything is computed (i.e. the number of computed objects is the same as the number of total objects). Red numbers indicate that the cache computation is still ongoing. To limit additional server load, the numbers can be updated on demand by clicking on the Update status button in the top right corner.

This feature relates to the list of available licenses, which can be accessed by navigating to   > Configuration > User management > License features. The list now includes a column Default, where you can see whether a license has been marked as default, i.e. whether it will automatically be assigned to all newly created users.

A license_information JSON field was added to the CustomToolVersion model to store the open source license information. The file is optional and can be null or blank.

This feature relates to the overview of add-ons, which can be accessed by navigating to   > Configuration > Add-ons. Now if users select an add-on in the grid and click on   to expand the side panel, they will see detailed, read-only information about the add-on.

This feature relates to the MDM requirements grid, which can be accessed by navigating to   > Configuration > MDM > Requirements. Now when users right-click on an MDM requirement in the grid, the context menu includes an option called Add-ons. This starts an add-on for the selected requirement(s).

This feature relates to the pop-up window that appears when navigating to   > Configuration > MDM > Test cases, right-clicking on an internal test case and selecting Duplicate from the context menu. Here, users see a grid, where they select the requirements that should be included in the new test case. The columns Result identifier, Description and Comment were added to this grid. These columns help users correctly identify the requirements, e.g. in situations when multiple requirements have the same name.

This feature relates to the list of users, which can be accessed by navigating to   > Configuration > User management > Users. The list now includes a column Assigned feature licenses. Here you can see which licenses are assigned to each user. You can also sort, group and filter the users according to their licenses.

Now that it is possible for users to create and edit projects under   > Configuration > Projects, other outdated possibilities were removed from  Project. Specifically, it is no longer possible to:

• create a new project by clicking on New project in the upper right corner.
• edit an existing project by opening the project and clicking on Settings in the left navigation bar.

This improvement relates to the process of adding MDM test cases to a project. In the past, if several test cases were selected at once, then the application would run into a timeout. The performance has been improved so that the process no longer ends with errors.

This improvement relates to the area for managing documents in  Project. In the past, the documents grid did not use the entire height available on the screen. That means, users only saw a few project documents before needing to scroll down. This has been improved. The area now uses the full available height.

Previously, cache records were deleted and re-inserted into the cache for each recalculation. Now, only the changed records are deleted, and the rest is using upsert to update existing records and insert new ones. This improves the cache calculation speed of both columns and scenarios. Also, by reducing unnecessary inserts, it also reduces the auto vacuum job which runs automatically on every new insert.

This improvement relates to the Select status target pop-up window, which appears when users set the values of a test or simulation in  Result as the status of requirements in  Project. The pop-up window now follows the same design guidelines as other areas of the application. This improves the user experience and makes the application more intuitive.

Users without licenses are blocked from accessing certain part of the application. In the past, the application only raised a generic permission error in such cases. That means, users could not tell whether they were lacking permissions or a license. This has been improved. The error messages now provide more detailed information.

This improvement relates to secondary buttons, e.g. the Cancel button in a confirmation dialog. In the past, these buttons were displayed without a border. Since they have a white filling and are displayed against a white background, they were not always recognizable as buttons. This has been improved by adding a border.

This improvement relates to areas where multiple tabs are grouped together, but only one tab is visible at a time, e.g. the test details panel in  Result, where users can see a test’s photos, video, documents, channels, etc. To improve performance, server requests are now only initiated for the active tab, rather than for all tabs.

This improvement relates to the upload files pop-up window, where users can select files that should be added to a test, e.g. documents, photos, videos and channels. In the past, the Upload button was already activated, even before the user had selected any files to upload. This has been improved.

The used type for the service is changed to ClusterIP. Depending on the used ingress class, adjustments to the provided annotation may be required.

This change was implemented for all date and time columns throughout the entire application, e.g. the Modified or Changed at columns within the MDM requirements grid. In the past, the column filters only took the date into consideration, but not the time. In some cases, this caused a mismatch between the filter and the result, e.g. filtering for tests with the date 9/23/2025 led to tests from 9/24/2025 being displayed. This occurred because of a timezone mismatch between the client and the server.

In the past, if a filter list only contained two options, e.g. the Star column in the  Result test grid, then users first saw a Choose one text, which needed to be extended to see the actual options. This was an unnecessary extra click, and it also differed from filter lists with more than two options, where the options were directly visible without the extra click.

This fix relates to the requirements grid in  Project. In the past, an error message was displayed if users right-clicked on an empty part of the grid and then selected Add-ons from the context menu. This has been fixed and the add-on now starts correctly. This is useful, e.g. for new projects where the user wants to start an add-on for custom import of requirements.

This fix relates to the process of adding requirements to a project. In the past, the new requirements were not immediately visible after being added. Users first needed to refresh the requirement grid. This has been fixed. The grid now automatically refreshes, i.e. new requirements are now automatically displayed.

This fix relates to the process of adding MDM test cases to a project. In the past and under specific circumstances, the test cases that a user selected were not later displayed in the Assign product variants window.

This fix relates to the requirements grid in  Project. In the past, the status summary was empty when the user selected one or more test cases in the grid. This has been fixed.

In the past, when creating a test in  Result, no life cycle state was assigned even if a life cycle state existed and it should have been used by default, i.e. the option Use this lifecycle as a default was activated. This has been fixed.

In the past, the life cycle state permissions were not checked when adding or changing the Owner field of a test. This has been fixed and life cycle state permissions are now respected.

This fix relates to the global roles, which can be accessed by navigating to   > Configuration > User management > Global roles. In the past, the Permissions area did not include any permissions for life cycle states. This has been fixed by adding the following permissions:

• Can change owner of tests
• Can demote tests
• Can promote tests

This fix relates to test attributes, which have corresponding MDM attributes of the type “Number” and which do not have a display unit. In the past, when viewing such test attributes in  Result, they were displayed as value [null], e.g. 17 [null]. This has been fixed so that the brackets are now completely omitted for values without a display unit.

This fix relates to the Test details page in  Result. Here, the Last modifed at timestamp tells users when the test was last modified. In the past, when users modified a test, the Last modified at timestamp was not automatically updated. Users needed to manually refresh the page in order to see the correct timestamp. This has been fixed.

This fix relates to the Projects window within the  Result test grid. In the past, the tooltip Add appeared when hovering the mouse over the   button. However, the tooltip did not disappear again until the page was refreshed. This behavior has been fixed. The tooltip now disappears when the cursor is no longer hovering over the button.

This fix relates to attachment panels, e.g. the Photos tab in  Result. In the past, if the tab included a large number of attachments with long names, and the user scrolled through the attachments, then the tooltips displaying the names were overlayed on top of each other, thus making them illegable. This has been fixed.

This fix relates to the project roles, which can be accessed by navigating to   > Configuration > User management > Project roles. It also relates to the life cycles, which can be accessed by navigating to   > Configuration > MDM > Life cycles. In the past, when users edited a project role, the corresponding life cycle state configuration was emptied. This has been fixed.

This fix relates to the MDM requirements, which can be accessed by navigating to   > Configuration > MDM > Requirements. In the past, when creating a new requirement, the threshold range -∞ to ∞ was shown as invalid, thus preventing users from saving their changes. This behavior has been fixed.

This fix relates to the life cycles states, which can be accessed by navigating to   > Configuration > MDM > Life cycles. Specifically, the error occurred when editing a life cycle and using copy-paste to modify the life cycle state permissions. In the past, the save button was not enabled after using copy-paste because the changes were not recognized. This has been fixed.

In the past and under certain conditions, users could see/use the private client states of other users, even though they did not have the ncessary permissions. This was the case for client states that had previously been public and which the user had used at some point in the past. This behavior has been fixed.

In the past, when creating or editing an object e.g. a status report template, users were able to select any of the disciplines. This was problematic because it meant that if the user did not belong to the discipline, then they would no longer able to see, edit or manage the object after saving.

It is now possible to disable the BlockOwnerDeletion for worker and runner-instances pods as this some RBAC permission are may which allow to define this value. By default, this is enabled but it can be disabled if required.

The verbs for the operator-worker and runner worker are now defined with actions instead of wildcards.

• CVE-2025-62718
• CVE-2026-40175
• CVE-2025-27152
• CVE-2026-25639
• CVE-2026-33937
• CVE-2026-33938
• CVE-2026-33939
• CVE-2026-33940
• CVE-2026-33941