Release Notes 8.24.x

Fixed a bug that caused the Test Cases module to fail to load for projects with a large number of test cases.

Fixed a bug that prevented users with the default Tester role and Test Suite Execute permission from adding Execution Comments in bulk, which resulted in an "insufficient rights" error.

Fixed a bug that caused some Azure DevOps–synced Requirements in QMetry to fail to open when custom fields contained special characters in their names.

Fixed a bug that prevented the Test Case module from loading for users in certain projects when the test case grid was sorted by Test Case Order and included risk-related fields.

Fixed a bug that prevented users from updating Custom Gadgets on Custom Dashboards when exactly one Date filter was used.

Fixed a bug that caused Global Filters to appear inconsistently in the “Test Execution Summary by Folder” System Report.

Fixed a bug that caused graphical chart based gadgets/reports to display the message “Report can't be viewed in chart format as query results in 500+ records” even after the gadget filters were updated to return fewer records.

Fixed a bug that caused Jira work items created outside the additional JQL filter to be incorrectly synced into QMetry with “In JQL/Filter Scope = No” after being updated in Jira.

Fixed a bug that caused previously saved advanced filters on the Test Suite “Link Test Cases” screen to duplicate instead of being removed on the first click after reopening the link dialog.

Fixed a bug that caused Platforms not to be copied when duplicating a Test Suite with Platforms assigned but no Release and Cycle, even when "Release and Cycle" was selected during the copy.

Fixed a bug that caused shared dashboards to be inaccessible when a co-owner (instead of the original owner) further shared them, redirecting users to “My Dashboards” with a “Dashboard does not exist” error.

Fixed a bug that caused JQL validation to fail incorrectly in QMetry when a JQL query contained the lowercase or operator.

Fixed a bug that caused project deletion to get stuck at and eventually fail with a timeout.

Fixed a bug that prevented the Azure DevOps work item type “Product Backlog Item” from appearing as a mappable issue type option in QMetry.

Fixed a bug that caused permission errors when accessing QMetry Project Settings in Azure DevOps projects for users assigned to the Project Administrators role through nested group membership.

Fixed a bug that prevented users from editing test steps when the Rich Text Editor (RTE) was enabled in migrated QMetry projects.

Fixed a bug that prevented users from integrating a Jira project in a migrated QMetry project by incorrectly displaying an “already configured” error, even when no Jira project mapping was visible in the UI.

Fixed a bug that caused the Requirements module to load infinitely when switching between modules and returning to it while a Jira requirement filter was applied at the sub-folder level.

Fixed a bug that caused some Jira Sub-task requirements to sync partially to QMetry.

Fixed a bug where “Export All Records” for Test Cases completed with an empty file and showed no record count.

Fixed a bug where users intermittently encountered an ‘AppMessages’ placeholder instead of the correct menu items upon logging out and back into QMetry, preventing proper navigation.

Fixed a bug where section and module names were not visible consistently across the QMetry UI after the Zephyr-QMetry migration.

QMetry now enables JQL-based syncing for each selected Jira Work Item Type configured with the Requirements and Issues module. This enhancement offers precise control over which Work Items sync into QMetry. When the JQL criteria are updated, any previously synced Work Items that no longer meet the scope will be appropriately tagged. If those Work Items later fall back within the JQL scope, the existing synced records will be re-associated.

For projects integrated with Jira, the Issues module list now includes three new columns showing the count of linked Test Case Executions, linked Requirements, and linked Test Cases for each Issue. This enhancement allows testers to quickly assess coverage and traceability from the list without needing to open individual Issue details.

Users with delete issue permissions can now remove Jira-synced issues from QMetry that no longer fall within the current JQL/Filter scope and are no longer required in QMetry. Deleting them in QMetry will not remove them from Jira.

When configuring Jira/Azure projects with a QMetry project, mapping Work Item Types to the Issues module is now optional. This enhancement simplifies project setup by allowing teams to integrate projects that contain only Requirement-level Work Item Types, without needing to map any Work Item Types to the Issues module.

The Search: Ask Me Anything feature now runs on SmartBear (QMetry) AI services, powered by a pre-trained Llama 3 model within the secure SmartBear ecosystem. This feature no longer uses OpenAI services and removes the dependency on OpenAI API keys for Super Admins to enable it on a QMetry instance. The transition enhances data security and offers direct cost benefits to customers by removing external OpenAI expenses.

Action Needed: Organizations that have enabled the QI Search feature and allowed configuration of documentation for project-specific searches must perform a mandatory "Refresh Content" for all files or URLs used as project documentation after this release. This step is essential to ensure that the search functions correctly and prevents any disruption in search results.

To ensure compatibility with QMetry Release v8.24, customers using Jira Data Centre must upgrade the QMetry Integration for Jira app to version 2.3.9 for Jira 10 or to version 2.3.9_jira9 for Jira 9 and earlier.

To ensure compatibility with QMetry Release v8.24, customers using Azure DevOps must upgrade the QMetry Test Management Extension to version 1.0.4.

Users must upgrade their QMetry Exploratory Testing browser extension to the latest version to ensure compatibility with QMetry Release 8.24. The latest versions of extensions are Chrome 1.2.10, Firefox 1.1.3, and Edge 1.0.9.

Fixed a bug that caused some Jira stories or issues to sync only partially with QMetry , resulting in some Jira items not being synced and requirements showing missing External Keys or displaying External Keys as plain text.

Fixed a bug where applying text formatting in Execution or Step Comments caused the entire comment to be replaced with a single character when using the Firefox browser.

Fixed a bug where accented characters in the Alias field for SSO users caused validation failures and unnecessary duplicate alias errors on profile updates.

Fixed a bug where asset share emails were not being triggered due to regex validation error on UI.

Fixed a bug where gadget-level filter updates in Advanced Query Report were not reflected in dashboard-level Global Filters on existing dashboards.

Fixed a bug where exporting QMetry System and Custom Dashboards as PDF resulted in blank PDFs, which also impacted scheduled reports.

Fixed a bug that caused project deletions to run indefinitely and fail with timeout.

Fixed a bug that caused custom table gadgets to reset to their default size after a page refresh.

Fixed a bug that caused the Total Estimated Time column on the Test Suites grid to show double the value when users copied a Test Suite using the “Link New Release and Cycle” option.

Fixed a bug that caused date filters to appear disabled when a tabular custom gadget included the @filter.release condition in its SQL query.