1.0.0

This feature relates to the status reports in  Project. Collaborative editing features were added, which allow users to work together on status reports. That means, multiple users can now contribute to a status report simultaneously. The status information of all users is collected before the status report is published.

This feature relates to the function for editing multiple MDM requirements or test cases. Specifically, it relates to situations when texts are not completely visible, because they are longer than the selection field. In such cases, users can now hover their mouse cursor over the truncated text. The full text is displayed in a tooltip.

This feature relates to the pages under   > Configuration > User management. These pages are now only visible to users who have been marked as staff. This change prevents “normal” users from being able to view sensitive personal information such as any email addresses, roles or dates when users last logged in.

This improvement relates to the status reports in  Project. Specifically, it relates to situations when users are working with a draft/private status report and are using edit mode to enter values into the requirements grid. Since the values of a draft status report can only be private, the Access column is now automatically set to private. The column is also disabled so that users can not change the setting.

This feature relates to the status reports in  Project. Users can now right-click on a private status report ( ) and select the option  Derive status report from the context menu. The current requirement values of this report are taken over to the new draft/private status report.

This improvement relates to the test attributes panel in  Result. Since it takes a lot of time to load over 5000 attributes for one test, only the relevant attributes, i.e. a filtered subset of attributes, should be displayed. Server-Side Row Model (SSRM) was implemented for this purpose. It loads blocks of rows when the user requests them, i.e. when the user scrolls or expands a group.

This improvement relates to the Set as project status option, which is displayed in the context menu of  Result. In the past, this option was visible to users who did not have sufficient rights to set the status. That means, the users could see and click on the option, but it failed due to insufficient rights. This has been improved. The option is now hidden to users with insufficient rights.

This improvement relates to the Report tab in  Result. The Select a report drop-down list now includes at option called No report selected. It is displayed at the end of list.

Use-case: This option is helpful in situations when a user has selected a test and viewed the test data in a report. Now the user wants to check something in many different tests at once. For example, the user might want to look up an attribute value in 100 different tests. Doing so while having a report selected could slow down the application massively. In such cases, it is helpful to deactivate the report for a moment.

This improvement relates to the context menus in the following areas:

•   > Configuration > MDM > Attributes
•   > Configuration > MDM > Requirements
•   > Configuration > MDM > Test cases
•   > Configuration > MDM > Attribute components
•   > Configuration > MDM > Attribute value lists
•   > Configuration > MDM > Attribute values
•   > Configuration > MDM > Calculation rules
•   > Configuration > Result > Presets
•   > Configuration > Result > Preset bricks
•   > Configuration > Result > Templates
•   > Configuration > Project > Status report templates
•   > Configuration > Add-ons
•   > Configuration > User management > Users
•   > Configuration > User management > Groups
•   > Configuration > User management > Access tokens
•   > Configuration > User management > Global roles
•   > Configuration > User management > Project roles

The context menus were compared and modified for consistency as needed. That means, e.g. they now all use the same wording, icons and order of entries. This improves the user experience and makes the application more intuitive.

This improvement relates to the page   >  About. The wording on this page was changed from “© 2010 - 2025 SCALE GmbH” to “© 2010 - 2025 SCALE GmbH. All rights reserved.”

This improvement relates to the Discipline drop-down lists in the following areas:

• Project product variants
• Share view in the project requirements, MDM requirements, MDM test cases and test grid
• Edit users

The Discipline drop-down lists now all use the same search component, which gives them a more consistent look and feel across the application.

This fix relates to the Edit project attributes page in  Project. In the past, the save button was disabled if a user selected an attribute in the field on the left, then cleared the attribute, and selected the attribute again. This behavior has been fixed. The save button is now enabled.

This fix relates to the requirements grid in  Project. Specifically, it relates to situations when users have grouped the requirements by multiple levels (e.g. by region, test case and directive). Within this grouped view, each group has an aggregated assessment color (e.g. red, yellow, or green). In the past, if the user then applied filters, e.g. to filter out all of the red entries, the grouping level still had the aggregated red assessment color. That means, the shown aggregation color did not update to match the filtered content. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, if the requirements were grouped, e.g. by test case, it was not possible to then filter the requirements by the Assessment column. This behavior has been fixed.

This fix relates to the project requirements that are derived from merging an MDM requirement with an MDM test case. In some edge cases, the context results in the explicit condition EQ None. Such context conditions are now accepted.

This fix relates to situations when users manually report the status of a project requirement in  Project. During the process, users can manually override the assessment color (indicated by the   symbol in the Assessment column). In the past, the color also changed in the Value column. However, there was no indication that the value color was manually changed and not based on the actual threshold. This has been fixed. The value now keeps the automatically assigned color, so that it always represents the automatic assessment based on the thresholds.

This fix relates to the function for adding test cases to a project. In the past, MDM test cases were not correctly added to a project under the following circumstances:

1. The user selected a group of several MDM test cases.
2. The user deselected a test case from this group.
3. The user clicked on   to add the remaining test cases to the project.

In this situation, the MDM test cases were not taken over into the project. This behavior has been fixed.

This fix relates to the plotting function in  Result. In the past, if two or more tests were selected, and these tests had the same code, then the channel was plotted twice. This behavior has been fixed.

This fix relates to the Attributes tab in  Result. In the past, users received an error when applying a filter to the Value column or when sorting the column content. This behavior has been fixed.

This fix relates to the test attachment grids in  Result, e.g. it relates to the tabs Documents and Channels. In the past, if a user selected a test with attachments, the panel sometimes used a line height of 42px instead of 28px. This behavior has been fixed.

This fix relates to the test grid in  Result. Now, if a user hovers their mouse cursor over a column in the grid, they will see a tooltip with a description. The tooltip is displayed if:

• an MDM attribute was used as the column definition,
• and if this MDM attribute has a description.

In the past, the tooltip was not always displayed. This has been fixed.

This fix relates to the Set as project status function in  Result. Specifically, it results to the Select status target pop-up window. In the past, the Base report drop-down list sometimes displayed private status reports. This behavior has been fixed. The drop-down list now only displays public status reports.

This fix relates to the attachments panel in  Result. Specifically, it relates to the check mark, which indicates whether a massdata file is available. In the past, this check mark was sometimes shown even though no massdata file was available. This behavior has been fixed.

This fix relates to the page for editing test attributes in  Result. In the past, the saved attributes were not automatically displayed in the list afterwards. Users needed to manually refresh the page. This behavior has been fixed.

This fix relates to the presets in  Result. In the past, when changing the preset, the default configuration of the workspace was loaded. That means, users needed to rearrange the workspace to restore their last configuration. This has been fixed.

This fix relates to the Edit tests window in  Result. In the past, the star icon did not change from starred to un-starred and vice versa when a user clicked on the star icon. This behavior has been fixed.

This fix relates to the context menus of MDM requirements and MDM test cases. In the past, the context menu options Activate and Deactivate were not working correctly. The action quit with the error message “Failed to toggle …”. This behavior has been fixed.

This fix relates to the menu   > Configuration > User management > Users. In the past, no icon was displayed when grouping the user accounts by state. This has been fixed. The Group column now correctly displays active/inactive icons.

This fix relates to the user content, which is displayed under   > Configuration > User content. In the past, the grid displayed the word ‘ERR’ when grouping the user content by the Tags column. This behavior has been fixed.