Upcoming

This feature relates to all grids, in which context attributes are displayed, e.g.:

• Project list
• Project requirements grid
• Add MDM test cases to project
• MDM requirements / MDM test cases

Now when a user moves their mouse cursor over the column header of a context attribute, they see a tooltip which displays the description of the MDM attribute.

This feature relates to the /project page, e.g. the URL https://example.eu/project. Previously, this URL opened the project list. However, starting in version 3.1.0, the project list was changed to a pop-up window. To ensure that  Project remains accessable, e.g. to users who use /project as their general access URL, the URL now opens the project list pop-up window as its own page.

This feature relates to the MDM test cases, which can be accessed by navigating to   > Configuration > MDM > Test cases. Previously, test cases supported two types of fields: fixed system fields (name, description, source, etc.) and context attributes used for requirement matching. A third type of field has now been added: descriptive attributes. They contain free-form descriptive information that is relevant for documentation, filtering, and grouping but that does not influence matching. The workflow for MDM admins is as follows:

1. Right-click on an MDM test case and select Add columns from the context menu.
2. In the Add columns pop-up window, select the descriptive attributes that should be added to the MDM test case and then click on Confirm.
3. The descriptive attributes appear in the Attributes column group.
4. Click on Edit mode and modify the attribute values as needed.

Project leads can then derive project test cases from the MDM test cases. The descriptive attributes and their values are inherited from the MDM test case. The descriptive attributes can be used to filter and sort the project requirements grid.

Note: This feature only enables the backend logic. That means, the function is not yet visible to users. This frontend logic will be enabled separately in the future.

This feature relates to the test details panel in  Result. It lays the groundwork for Report Designer to be displayed in its own panel in the future.

This feature relates to the test grid in  Result. Specifically, it relates to the Evaluate tests function, which is still in the process of being developed, and which allows users to see a color-coded evaluation of key test results in the grid. Previously, when evaluating tests, the first matching project test cases was used. That means, if a user had multiple test cases with identical context conditions, then the user could not be sure which test case would be used. This has been changed.

• If multiple project test cases match a test, the one with the alphabetically last name is used. Example: “AAA (suffix)” is selected over “AAA”.
• If exactly one test case matches, the behavior is unchanged.
• If no test case matches, the behavior is unchanged.

This feature relates to the Import tests context menu entry, which appears when right-clicking on a project in  Result. To prevent confusion, this context menu entry is now disabled if the application does not have any add-ons for importing tests.

This feature relates to the Attributes tab in the  Result test grid. In previous versions, users were able to export the attributes here in CSV/Excel format. This functionality has since disappeared and is now being re-enabled.

Note: This feature only re-enables the backend logic. That means, the function is not yet visible to users in the Attributes tab. This frontend logic will be re-enabled separately in the future.

This feature relates to the test grid in  Result. A new Preview tab was added to the workspace, which automatically displays selected attachments, e.g. photos and videos. In general, if a user selects one or several attachments, then the Preview tab displays these attachments immediately. The attachments are displayed:

• As a carousel (if more than one attachment selected).
• Along with the file name.
• With arrows (to navigate between the preview images if more than one attachment is selected).
• As a placeholder image if the selected element does not have a preview, e.g. file types other than phots and videos.

This feature relates to the project management grid, which can be accessed by navigating to   > Configuration > Projects. It also relates to the disciplines grid , which can be accessed by navigating to   > Configuration > User management > Disciplines. When using Edit mode, users can now right-click on a row in the grid and select Delete from the context menu. This marks the row for deletion, i.e. the row is grayed out and displayed with a   symbol in the far left column. A chip at the bottom of the screen indicates how many rows that have been marked for deletion. The rows are finally deleted when clicking on   Save.

Note: This feature is currently only available in the project management grid and the disciplines grid. It will become available in additional grids in the future.

This feature relates to the jobs list, which can be found by clicking on   in the toolbar or by navigating to   > Configuration > Jobs.

Users can now cancel running or pending jobs by right-clicking on a job and selecting   Cancel job from the context menu.

Note: This option is only available for running and pending jobs (State column displays   or   icon). The option is grayed out for all other types of jobs.

Use-case: Users might want to cancel a job that doesn’t come to an end (e.g. due to add-on reasons or backend reasons) and blocks a runner until the job finally runs into a timeout. This is especially true on instances with few (over even only one) runners. If the jobs aren’t cancelled, then they will wait for timeout one after the other, which is a huge blocker if only one runner is available.

New helm values were added for defining tolerations, affinities, nodeselectors on pod or global level.

This improvement relates to the requirements grid in  Project. Specifically, it relates to the process of reporting a status in the Properties window, while using edit mode or while using the Set as project status function. Previously, users were able to manually enter an assessment before they entered a value. Since this is not the correct workflow, users are now prevented from doing so. Now users can only manually enter an assessment for requirements that already have a value.

This improvement relates to the process of assigning product variants to test cases. Previously, selecting a variant automatically unselected the checkbox in the No variant column and vice versa. This has been changed to accomodate scenarios where a test case should be added to a project without any product variation, and additionally with assigned product variants.

This improvement relates to the requirements page in  Project. Specifically, it relates to the default layout, which is hardcoded and can be restored by clicking on Workspace > Reset layout in the tool bar. The Status reports panel was moved to the left side of the screen so that it better matches the user workflow and reading direction:

• Status reports (left): The user first selects a status report.
• Requirements (middle): The user adds status information.
• Properties (right): The user views detailed information.

This improvement relates to starred projects, which can either be opened from the list of projects or from the toolbar. Previously, when opening a starred project from the toolbar, users landed on the project overview page, rather than on the project requirements page. This has been improved. Users now land on the project requirements page.

This improvement relates to the views in the  Result test grid. Previously, views created within one preset could be selected while a different preset was active. This has been fixed. Users now only see the views that are compatible with their currently selected preset.

This improvement relates to the Select projects window, which can be accessed by navigating to  Result and clicking on   in the upper right corner of the Projects window. The projects are now displayed as a grid. This allows users to filter, sort and group the projects in the list more easily.

This improvement relates to add-ons that create PDF reports and then display the file. Previously, it took a long time between finalizing the document and displaying the preview. Users did not receive any feedback during this time. This has been improved.

Previously, the scale board library was used to compare photos, videos and to plot channels in  Result. It has been replaced by the Report Designer add-on. This reduces the bundle size of the main application and removes the dependency between the main application and scale board. Furthermore, the superfluous Report designer option was removed from the test grid context menu.

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.

This improvement relates to situations when users edit MDM test cases from the MDM requirements grid. That means, when users navigate to   > Configuration > MDM > Requirements, group the MDM requirements by test case, right-click on a test case and select Edit test case. After editing the MDM test case, the user either clicks on save or cancel. Previously, the user was then redirected to the MDM test cases grid, rather than the MDM requirements grid where they came from. This has been improved. After editing, users are now correctly redirected back to their previous page.

Previously, long annotation names for RdTest SSRM led to a warning in the log due to the postgres limit. Long names are now truncated.

This change relates to the project list in  Project. The project list now opens in a pop-up window. The projects within this window are now displayed as a grid. The grid layout allows users e.g. to group and filter the projects for a better user experience.

Previously, the pages under   > Configuration > User management were only visible to users who had been marked as staff. This staff dependency has been removed. The pages are now visible to users who have the “can view user” permission.

This fix relates to the project management grid, which can be accessed by navigating to   > Configuration > Projects. Specifically, it relates to situations when using Edit mode. Previously, users could select cells, copy them and paste their values elsewhere in the grid. But if the user then tried to select, copy and paste the cells that were just pasted, the grid displayed an error. This has been fixed. Previously pasted values can now also be copied and pasted.

This fix relates to the list of projects, which can be accessed by navigating to   > Configuration > Projects. Previously, the grid displayed ERR when trying to group the projects by an attribute, whose identifier contained spaces. For example, the attribute identifier Example name would cause an error, while the attribute identifier Example-name would not. This has been fixed.

This fix relates to add-ons that are displayed in their own panels. Previously, after a fresh page load (reload, new tab, login), such add-on panels were missing from the dashboard and from the  Result > Workspace menu. This has been fixed.

This fix relates to the test grid in  Result. Specifically, it relates to tests with an incorrectly formatted “date” attribute value (e.g. month, date and year in the wrong order). If the corresponding Date column was then displayed in the test grid, the application stopped displaying any tests at all. This has been fixed.

An event atachment is essentially a zip file containing, e.g.:

• JSON file with all meta information
• Thumnail picture
• Movie
• 3D data

Previously, formally correct archives were not being processed correctly. All of the meta data from the included JSON file was missing. The JSON file was not being processed. This has been fixed.

This fix relates to the test templates, which can be accessed by navigating to   > Configuration > Templates > Test templates. Previously, users were only able to enter obsolete (inactive) attributes into the Identifier field. This has been fixed. Active attributes can now also be added to test templates.

This fix relates to the MDM requirements grid, which can be accessed by navigating to   > Configuration > MDM > Requirements. Specifically, it relates to the filters Blank and Not Blank. Previously, these filters produced incorrect results. This has been fixed so that the filters now work correctly.

This fix relates to edit mode, e.g. in the  Result test grid and in the project list under   > Configuration > Projects. Previously, cells were marked as having been modified, even though no change was made. This occurred if a cell was selected but the value was not changed. It also occurred when using Clear on an already empty cell. This has been fixed.

This fix relates to the MDM attribute value lists, which can be found by navigating to   > Configuration > MDM > Attribute value lists. Previously, when editing an attribute value list, no values were displayed in the Values section, even though values existed. The values were not displayed until searching for values or adding additional values. This behavior has been fixed. The values are now immediately displayed when opening the edit page.

This fix relates to the Project roles area of the My profile page, which can be accessed by navigating to   > My profile. Previously, if a user expanded the sections in the Project roles area, then they automatically collapsed again after a few seconds. This has been fixed.

This fix relates to the MDM attribute value lists, which can be found by navigating to   > Configuration > MDM > Attribute value lists. Previously, after grouping by any column, the grid did not display any content and the grouped column could no longer be removed, forcing users to refresh the page. This has been fixed. The data can now be grouped as expected.