0.57.0

This feature relates to the attributes page in  Project. The page is now divided into two different sections: Common attributes and Product variants.

• Common attributes: Here, users can save attributes for the entire project, i.e. for all of the product variants.
• Product variants: Here, users can create and manage product variants. For example, users can add, remove and edit variants in the grid. Furthermore, users can save context attributes for each individual variant.

This feature relates to the function for adding MDM test cases to a project. Now, a pop-up window opens after users have selected the appropriate MDM test cases and clicked on the save icon. In this pop-up window, users can select which product variants each test case applies to. In the example below:

• “Test_Case_1” will be added to the project. It will be assigned to the variant called “Variant 1”.
• “Test_Case_2” will be added to the project twice. It will be assigned once to “Variant 2” and once to “Variant 3”.

This feature relates to the function for editing a test case to be project-specific. The test case edit page now includes a field called Product variant. Note: This field is read-only.

This feature relates to the function for comparing project test cases with their MDM equivalents. In the past, the compare dialog did not take disciplines into account. This behavior has been changed.

This feature relates to the requirements grid in  Project. Specifically, it relates to the function for adding test cases to a project. In the past, when a user imported a test case into a project, only the active requirements of the test case were imported. This behavior has been changed. Now, users can specify if they want the inactive requirements to be imported as well. This is done by right-clicking on a test case and selecting the option Take over inactive requirements from the context menu.

This feature relates to the requirements grid in  Project. If the requirements are grouped, e.g. by test case, users can now right-click on a group and access the  Add-ons entry in the context menu. This means, add-ons can now be executed for entire groups of requirements, rather than just for one single requirement.

This feature relates to the requirements grid in  Project. If the requirements are grouped, e.g. by test case, users can now click on a group and then click on   to see a status summary for the requirements within that group. The status summary displays:

• The number of requirements that have a status (example: 11)
• The assessment color for the entire group (example: yellow)
• The number of requirements without a status (example: 13)
• The number of requirements with each assessment color (example: 4 yellow, 7 green)

This feature relates to the function for comparing project test cases and requirements with their MDM equivalents. In the past, users sometimes saw that changes had been made, but they were not able to tell what exactly those changes were. For example, if a line break or an empty space was added to the description, it looked like the old and new description were identicial. This behavior has been changed. Users can now activate the option Highlight changes. This displays additional highlighting and visual clues, so that users can more easily identify the differences.

This feature relates to the test grid in  Result. Specifically, it relates to the Videos tab. Here, users click on   to display the videos as a list, and then select the relevant videos (ctrl. + click). Now, when users right-click, the context menu contains an option called Compare Videos. This option allows users to compare videos side-by-side. For example, users could compare the changes in various design versions.

This feature relates to the grids found within the set as project status function. Now users can highlight cells by holding down the left mouse button and moving their mouse cursor over the cells. Furthermore, users can copy the content of the highlighted cells (Ctrl + C).

This feature relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. It also relates to the MDM requirements, which are found under   > Configuration > MDM > Requirements. Once an MDM test case or an MDM requirement has been added to a project, it can no longer be deleted. This means, when a user right-clicks on the MDM test case or on the MDM requirement, the context menu no longer includes the option  Remove.

This feature relates to the MDM grids, which are found under   > Configuration > MDM. Now users can highlight cells by holding down the left mouse button and moving their mouse cursor over the cells. Furthermore, users can copy the content of the highlighted cells (Ctrl + C).

This feature relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. Users can click on a test case in the overview and then click on   to expand a side panel, which contains details about the test case. This side panel now includes an area called Attachment. Here, users can manage any relevant attachments for the test case. That means, users can upload new attachments, download existing attachments or delete existing attachments.

This feature relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. When editing a test case, the Requirements area now includes a column called Selection info. This column allows users to check which requirements are assigned to the test case and which are not. Users can group, sort and filter for requirements that are selected or not selected.

This improvement relates to the documents area in  Project. Specifically, it relates to the   button for uploading new documents. In the past, this button was displayed regardless of the user’s permissions. This behavior has been changed. The button is now only visible to users who have the permission Can view project document.

This improvement relates to all of the grids that use the view feature, e.g. the test grid, MDM requirement grid and project requirement grid. Once a user has clicked on   and selected the option Save as new, the view is automatically selected.

This improvement relates to the calculation rule configuration page, which can be accessed by navigating to   > Configuration > MDM > Calculation rules. The list of calculation rules was modified. It now has a more consistant look and feel, and it matches other pages more closely.

This improvement relates to the user list, which can be accessed by navigating to   > Configuration > User management > Users. The list of users has been changed to an AG grid. This is advantageous for two reasons:

• It gives the application a more consistant look and feel, as AG grids are also used in other menus.
• The AG grid has additional features, such as the ability to filter, sort or group columns.

This improvement relates to the menus   > Configuration > MDM > Test cases and   > Configuration > Project > Status report templates. In the past, these menus showed the user name in the Modified by column. This has been changed. The column now shows the display name along with the user name in parenthesis, e.g. displayName (userName).

This fix relates to the function for comparing project test cases and requirements with their MDM equivalents. In the past, if a user duplicated a requirement and then tried to compare the duplicate with its MDM equivalent, the user received the error Failed to compare to parent. This behavior has been fixed.

This fix relates to the project image, which is displayed in the Overview and in the left sidebar of  Project. In the past, when users uploaded a new project image, the new image only appeared in the overview. The new image did not appear in the sidebar until the user reloaded the page. This behavior has been fixed. Now when uploading a new project image, the image correctly appears in both areas.

This fix relates to the ability to copy a value in one column and paste it into another column. In the past, if the value with a display unit was copied, e.g. 100.0 km/h, then its value in SI-units was pasted into other columns, e.g. 27.8 m/s. This behavior has been fixed.

This fix relates to the Edit tests function in  Result. In the past, if a user double-clicked on a cell to edit it, then the value was suddenly displayed as an SI-unit. For example, if the user double-clicked on the speed 100.0 km/h, then this value was suddenly displayed as 27.77777778. This behavior has been fixed.

This fix relates to the test grid in  Result. Specifically, it relates to an error that occurred if the user selected a project in the upper left corner and then clicked on the filter icon in a column header ( ). In this case, the user received the error message Failed to load values. This behavior has been fixed. The list of filter values now loads correctly.

This fix relates to the requirements grid in  Result. In the past, users occasionally received an error message (ERR) when expanding a group. Specifically, the error occurred if the user created several different grouping levels, sorted the requirements by the first grouping level, and then expanded the first group. This behavior has been fixed.

The behavior is now the same as when creating a single test attachment or updating via graphql.

This fix relates to the user permission tree, which is found under   > Configuration > User management > Users. The tree is visible when you open a user account and scroll down to the Permissions area. In the past, the arrows ( ) that expand and collapse sections of the tree were invisible. This has been fixed.

This fix relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. In the past, if a user right-clicked on a test case and selected Copy from the context menu, the copy was sometimes created with different MDM requirements than the original. This behavior has been fixed.

This fix relates to the MDM requirements grid, which is found under   > Configuration > MDM > Requirements. In the past, if a user right-clicked on a requirement and selected Copy from the context menu, then the requirement was copied without any relation to a test case. This behavior has been fixed. The test case information is now copied as well.

Further information can be found in the Django Forum Post: https://forum.djangoproject.com/t/timestamp-inconsistencies-when-using-postgresql-with-pgpool/34716

The management backup command didn’t work correctly while using s3 as backup option because of a misconfiguration of the s3 paths for the db and the media folder. This has been fixed.