Upcoming

This feature relates to the status reports in  Project. Because a status report is a snapshot of the project requirements at a specific time, users should not be able to modify the project requirements while a status report is selected. Changes should be made in the overall project scope and captured in newly derived reports.

To make this possible, the context menu options for editing project requirements are now deactivated while a status report is selected. Note: These options were deactivated on the project requirement level, the test case level and the group level.

This feature relates to edit mode in the  Result test grid. Previously, when users pasted invalid values (e.g. from an Excel spreadsheet) into the test grid, they were not able to save their changes, but they also did not receive an error message indicating what went wrong. Now when users paste values into the test grid, the content is directly validated and any errors are highlighted. This gives users immediate feedback before they click on the save button.

This feature relates to the add-ons side panel, which can be accessed by navigating to   > Configuration > Add-ons, selecting an add-on in the grid and clicking on  . The side panel now contains an Open source licenses area, which displays e.g. the license type and copyright information of any open source licenses that are applicable to the add-on.

Edit mode now supports a read-only setting to disable editing (and hide the edit mode UI). This is useful if a business context does not allow changes, e.g. public status report or missing permissions. If [readOnly]="true", the edit action bar is hidden and the grid cannot enter edit mode (via button or programmatically). Grids that do not use [readOnly] are unaffected.

This feature relates to the notifications, which can be accessed by clicking on the notifications icon ( ) in the toolbar. A job notification is now created when an add-on run finishes. The notification state corresponds to the end state of the add-on run i.e. failed states to error, success states to success.

Some workflows exceed the 60 second single-request limit, e.g. complex calculations (like matching context conditions), export generation, archive collection, and importing test cases or requirements into projects. To provide timely user feedback, these operations are now run asynchronously outside the normal request-response cycle.

Users can now access the Add-ons menu entry from the toolbar of both  Project and  Result. In the past, the Add-ons entry was only visible within  Result.

Evaluating the policies of other users can be done by passing the user ID of the target user in the policy query:

{
  w3syseProjectPolicy(userId: "ABCdefG1aBC2DEFxZTA2ABCDeF2Mi00ABC1DEF0YzQtABCdEfGhZYXwVuTs") {
    canCreate
    canRead
    canUpdate
    canDelete
    canCreateProjectTestCase
    canCreateMilestone
  }
}

If the requesting user does not have the view_user permission on the target user, then a PermissionDenied error is raised.

This allows e.g. tests that are synchronized from external systems to be imported or updated with their correct life cycle state. Furthermore, non-neighboring state transitions are now supported. Internally, a state-by-state step-wise transition is used.

This improvement relates to edit mode in the  Result test grid. Previously, when a user saved their changes, the values were saved as test attributes but the grid did not immediately reflect the changes. This gave users the impression that the save had failed. Change processing times have been improved so that the values now appear immediately.

This improvement relates to the test grid in  Result. Users now receive consistent feedback for any actions that fail due to insufficient permissions or errors. This helps improve transparency and reduce confusion.

Rendering and interaction performance in the  Result test grid was improved, particularly for grids with many rows or columns.

This improvement relates to the test grid in  Result. In the past, the test grid reloaded when a user added a test to a collection or removed a test from a collection. This caused unnecessary waiting time and it caused the user to lose the current scroll bar position. This has been changed to improve the user experience.

The new entries_list field was introduced for the MdmAttributeValueListType, which returns all values in the value list of the MDM attribute. This improves query performance and simplifies access patterns. The field entries is now considered deprecated and will be removed in the next major release.

Python package dependencies are routinely updated. This keeps the application current with security patches, bug fixes, performance improvements, and new features from the open-source ecosystem.

Related fields are now prefetched while deriving project test cases. This improves the performance.

This improvement relates to the MDM attributes, which can be accessed by navigating to   > Configuration > MDM > Attributes and to the presets, which can be accessed by navigating to   > Configuration > Preset > Presets. When creating MDM attributes or presets, users can select a discipline, which is essentially a filter (users only see data that matches their own disciplines). Previously, users were able to see MDM attributes and presets belonging to other disciplines. This is now enforced consistently. Note: Super users continue to see objects for all disciplines.

Previously, when an action failed due to insufficient permissions, users only saw a generic ‘You do not have permission to perform this action’ message. Error messages now state exactly which permission is missing.

This improvement relates to the add-ons, which can be started by right-clicking on a line in the  Result test grid and selecting Add-ons from the context menu. Previously, when uploading a new version of an add-on, it appeared in the context menu immediately after reloading the test grid. However, the new version could not necessarily be started right away and trying to load it caused an error. This behavior has been improved. New versions are now disabled while still being generated.

The add-on developer documentation was reviewed and updated to reflect the current workflow.

This improvement relates to the MDM attributes grid, which can be accessed by navigating to   > Configuration > MDM > Attributes. In the past, there were differences between the columns displayed in MDM attributes grid and the input fields displayed when adding or editing an MDM attribute. The following changes were made to ensure consistency:

• MDM attributes grid:
  • The Component name column was renamed Component.
  • Description and Comment columns were added.
• MDM attributes edit page:
  • The Obsolete checkbox was replaced with a State drop-down list.
  • The Discipline input field was renamed Disciplines.

This improvement relates to dialogs, such as the Data analysis add-on. In the past, there was empty space between the header and the add-on. This visual spacing was reduced to improve the user experience.

Unnecessary field loading and per-instance database queries were removed from the change-tracking pipeline, which reduces the database load.

Previously, uploading multiple attachment files was very slow. To improve performance, a copy of the uploaded files is now delegated to a background job.

Redis socket timeouts are now explicitly configured across the server, worker and operator-worker:

• Default Redis connections (server caches and operator-worker): socket_timeout is set to 30 seconds. On timeout the connection is retried automatically, so no fallback is required.
• Channel layer (channels_redis): socket_timeout is set to 60 seconds. The channel layer host is now configured as an explicit dict so the timeout can be applied per-host. Prior to redis-py 8.0.0 this defaulted to no timeout; 8.0.0 introduced a 5-second default which was too aggressive for long-lived WebSocket connections.

The Helm chart previously supported Kubernetes 1.24 and higher. This has been changed. The minimum supported version is now 1.30.

The worker-customtools-python image is no longer provided as a runner default. You must now configure a default image via worker.runner.defaultImage for add-ons that do not bundle their own image.

The Redis subchart is no longer provided via the scale-result+scale-project Helm chart. It is necessary to use another Redis or ValKey Cache Backend System prior to using this or newer versions.

This fix relates to the requirements grid in  Project. Previously, grouping the requirements grid by the Assessment column produced an error. This has been fixed.

This fix relates to the process of adding MDM test cases to a project via the Add MDM test cases to project dialog. Previously, the procedure could silently fail because pagination returned duplicate IDs. This has been fixed.

This fix relates to the export summary function in  Project. In the past, when filtering the project requirements by a status report, the export summary displayed the requirements from the overall scope, rather than from the status report. This has been fixed.

This fix relates to the status summary in  Project. Previously, the status summary was empty after selecting a status report. This has been fixed. The status summary now displays the correct information, regardless of whether the requirements are filtered by a status report.

This fix relates to the process of adding MDM test cases to a project. Previously, when adding test cases, the user only saw a pop-up window displaying processing feedback for a very short time. Then the window closed and the user did not have any further feedback about the status of the ongoing process. This has been fixed. The pop-up window now remains open while the test cases are being added to the project. This gives the user feedback that the process is still ongoing.

This fix relates to the list of projects, which can be accessed by navigating to   > Configuration > Projects. Since the project name is a mandatory field, users now see an error message if the Name cell is empty. The save button is also disabled until a name has been entered.

This fix relates to edit mode in the  Result test grid. Previously, using Clear on an already empty cell marked it as edited and produced an error upon saving. This has been fixed.

This fix relates to the column headers in the  Result test grid. Specifically, it relates to those columns that are defined with a preset and whose header name includes a conditional line break (­). Previously, such columns were displayed correctly in the grid and in the list of columns that appears when clicking on  . However, when searching for the column name, such columns were previously excluded from the search results. This has been fixed.

Previously, channels whose header contained a non-numeric value such as Time of first sample: NOVALUE could not be plotted in Report Designer. Non-numeric values are now interpreted as 0, and the channel is plotted normally.

This fix relates to edit mode in the  Result test grid. Previously, if a user copied cells from a spreadsheet (e.g. Excel or LibreOffice) whose selection ended with a line feed, then pasting those cells into the test grid also cleared the cell in the following row. This has been fixed. Trailing line feeds are now stripped before pasting.

This fix relates to edit mode in the  Result test grid. Previously, activating edit mode, double-clicking a cell to open a drop-down list, and then typing to filter the options caused an error that disabled further editing and required a full page reload. This has been fixed.

An internal KeyError that could interrupt file downloads under specific conditions is now handled gracefully.

This fix relates to the add-ons, which can be accessed by navigating to   > Configuration > Add-ons. Here, add-ons that can be triggered manually are displayed with a play button. Previously, all add-ons could be run manually by clicking on the empty cell where the play button would otherwise appear. 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 cycle states, which can be accessed by navigating to   > Configuration > MDM > Life cycles and looking at the Life cycle states area within a life cycle. Previously, if a life cycle state was configured with permissions for a specific project role, then any edit to that role (even an unrelated one) emptied the life cycle state configuration. This has been fixed. Edits on the project role page no longer affect the life cycle state configuration.

This fix relates to the profile page, which can be accessed by navigating to   > My profile. Previously, the Access tokens area was only visible to superusers. This has been fixed. Now all users who have the relevant permissions (can view access token and can add access token) are able to view and add access tokens.

Mixing null values and empty strings in string-based columns can cause issues, e.g. when grouping by such a column. A migration was added to prevent such issues.

Previously, client state tags could be deleted or modified in ways that bypassed intended permissions. This has been fixed so that CRUD operations on discipline tags are now properly restricted.

This fix relates to the MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases. Previously, users could save a test case even if a context field was invalid. For example, users could add a context attribute without assigning a mandatory Value. Saving is now blocked when any context condition is invalid.

This fix relates to the user notifications, which can be accessed by clicking on the notifications icon ( ) in the toolbar. In the past, users were not able to mark notifications as read, since the permission check always failed. This has been fixed. Users are now able to mark their notifications as read.

This fix relates to the MDM requirements, which can be accessed by navigating to   > Configuration > MDM > Requirements. In the past, when a user right-clicked on a requirement and selected Duplicate from the context menu, a copy of the requirement was created but its context was left empty. This has been fixed. The context of the requirement is now correctly copied as well.