Upcoming
Release date:
New feature MISC | If a text is truncated in the 'Multi edit' window, users can now see the entire text in a tooltip.
[#7524] 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. |
New feature MISC | The 'Multi edit' window now includes operations for adding and removing attribute values.
[#7501] This feature relates to the function for editing multiple MDM requirements or test cases. Specifically, it relates to the Operation drop-down list within the Context tab. The drop-down list now includes the operations Add attribute value and Remove attribute value. Use-case: Imagine you have three MDM requirements with context “DEMO = A” and four with context “DEMO = A, B”. You can use the operation Add attribute value to add “DEMO = C” to all of the requirements. At the end, three MDM requirements will have “DEMO = A, C” and four will have “DEMO = A, B, C”. ![]() |
Improvement PROJECT | Improvements were made to the product variant selection when adding test cases to projects. The improvements include better loading feedback. ] |
Improvement RESULT | Users are now able to deselect reports.
[#7504] This improvement relates to the Report tab in
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. |
Improvement MISC | Context menus were modified for consistency in the 'MDM' area. They now all follow the same design guidelines.
[#7497] This improvement relates to the context menus in the following areas:
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. |
Improvement MISC | Context menus were modified for consistency in the 'Status report templates' and 'Add-ons' areas. They now all follow the same design guidelines.
[#7500] This improvement relates to the context menus in the following areas:
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. |
Improvement MISC | Context menus were modified for consistency in the 'User management' area. They now all follow the same design guidelines.
[#7499] This improvement relates to the context menus in the following areas:
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. |
Improvement MISC | Context menus were modified for consistency in the Result configuration area. They now all follow the same design guidelines.
[#7498] This improvement relates to the context menus in the following areas:
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. |
Improvement MISC | The 'Discipline' drop-down lists were modified for consistency across the application.
[#7457] This improvement relates to the Discipline drop-down lists in the following areas:
The Discipline drop-down lists now all use the same search component, which gives them a more consistent look and feel across the application. |
Feature change DEPLOYMENT | The used PostgreSQL client was updated to version 16. [#6964] |
Bug fix PROJECT | Duplicated project test cases no longer throw an error in the side panel.
[#7496] This fix relates to duplicated test cases in
|
Bug fix PROJECT | It is now possible to save project attributes that have been deselected and reselected.
[#7494] This fix relates to the Edit project attributes page in
|
Bug fix PROJECT | Project requirements can now be filtered by assessment color while grouping is in place.
[#7509] This fix relates to the requirements grid in
|
Bug fix PROJECT | The context condition 'None' is now an accepted value.
[#7544] 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 |
Bug fix PROJECT | When adding test cases to a project, the click order no longer affects the selected test cases.
[#7047] 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:
In this situation, the MDM test cases were not taken over into the project. This behavior has been fixed. |
Bug fix RESULT | Test attachment grids now have a fixed line height of 28px.
[#7554] This fix relates to the test attachment grids in
|
Bug fix RESULT | Users are now able to star and un-star tests in the 'Edit tests' window.
[#7478] This fix relates to the Edit tests window in
|
Bug fix MISC | MDM requirements and test cases can now be activated/deactivated again correctly.
[#7573] 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. |
Bug fix MISC | The user configuration grid now displays an active/inactive icon when grouped by state.
[#7533] This fix relates to the menu |