Release Notes 8.25.x

Fixed a bug that caused the user deactivation or deletion to fail when user credentials were configured in an inactive/expired Jira Server instance, preventing the action from completing successfully.

Fixed a bug that caused misleading error messages to be displayed while creating or editing Jira issues from QMetry when the user configured Jira API credentials were expired or revoked.

Fixed a bug that caused users to receive insufficient permission errors while editing or updating Shareable Test Cases in cloned projects, despite having the required permissions.

Fixed a bug that caused new version creation for Approved Test Cases to fail in Bulk Operations for e-Signature enabled projects when no field updates were selected, incorrectly preventing users from creating a new version.

Fixed a bug that caused execution comments to intermittently fail to save in test suites containing a large number of test cases.

Fixed a bug that caused users without the required customization permissions to appear able to update customized Notification settings, even though the changes were not saved.

Fixed a bug that caused test case creation to fail when a user-defined field (UDF) name matched a reserved QMetry system field.

Fixed a bug that caused the latest edits or changes in test case step fields (such as Step Description, Input Data, or Expected Outcome) to not be saved if the Update button was clicked while the cursor was still active in a text field.

Fixed a bug that caused Jira integration failures, preventing Jira updates from synchronizing correctly to QMetry and causing exceptions in the Project Integration, Requirement, and Issues modules.

Fixed a bug that caused the "Forgot Password" page to display a generic error message when an incorrect username or organization was entered.

Fixed a bug in Advanced Query Reports where User Defined Fields (UDFs) configured at the Test Case Step level were incorrectly appearing as null.

Fixed a bug with the Azure Add-on integration where the configuration was not retained after initial setup, causing the QMetry Test Coverage section in Azure work items to fail to load properly and display “Not Logged In” errors.

Fixed a bug that incorrectly blocked users from logging in with a concurrent user limit error even when the configured license limit had not been exceeded.

Fixed an issue that caused the Bulk Edit screen in the Test Case module that prevented all editable fields from appearing in cloned projects.

Fixed an issue that caused Advanced Query Reports in QMetry Insights to time out or respond slowly while executing queries on large datasets.

QMetry has upgraded its database to MySQL v8.4.8, resulting in improved performance, enhanced security, and increased reliability.

Fixed a bug that caused deleted Jira issues to remain visible in QMetry custom reports when customers deleted defects or requirements in Jira.

Fixed a bug that caused the Test Case module/grid to remain stuck in a loading state when multiple custom field filters were applied.

Fixed a bug that caused users granted project access via SCIM to be prevented from accessing the Test Case module in projects with Risk Analysis feature enabled.

Fixed a bug that caused the QMetry panel in Jira Cloud to intermittently fail to load, displaying a misleading “Not Logged In” message, and temporarily hang while loading Jira integration projects in the Projects → Integration tab in QMetry after the Forge add-on migration.

Fixed a bug that caused Export Test Execution Details (PDF/Word) to ignore applied filters and export all records, and display an incorrect “Executed At” timestamp (defaulted to 00:00:00) in the exported file.

Fixed a bug that caused intermittent false “Hourly API rate limit reached” errors even when usage was below the configured threshold.

Fixed a bug that caused the bulk test case folder copy operation to partially complete when shareable test cases were present in selected folders, resulting in those and subsequent test cases being skipped.

Fixed a bug that caused intermittent query execution errors in custom dashboard gadgets when queries contained the INTERVAL keyword.

Fixed a bug that caused Jira Fields Configuration selections made during initial Jira project setup to not be retained and requires clicking Save & Activate.

Fixed a bug that caused performance issues with slow loading of the “Available Issue(s)” tab while linking Jira issues.

Fixed a bug that caused the “Execution Archived” flag in QMetry Insights (Advanced Reports) to remain false when users archived a Test Suite, causing incorrect data in reports.

Fixed a bug that caused SQL-based custom dashboard gadgets to intermittently fail to load results when multiple gadgets using REGEXP queries were added to the same dashboard.

For Jira Cloud Customers (Connect on Forge Migration):

For Jira Data Center Customers (v11 Support):

Fixed a bug that caused manual full syncs for certain Jira-integrated requirements and issues to fail, preventing some work items from syncing to QMetry.

Fixed a bug that caused ATG test case generation to fail when processing requirements with long and heavily formatted descriptions.

Fixed a bug that prevented users with a Read-Only license from accessing certain modules due to incorrect permission errors.

Fixed a bug that caused Bulk Update operations on Test Cases to fail when updating test cases with existing Labels.

Fixed a bug that prevented users from viewing/adding attachments on the Test Execution screen for cross-project linked Test Cases.

Centralised Automation Management: Link multiple Reflect instances to QMetry for a unified view of automation assets across teams and environments.

Automatic Test Case Synchronisation: Tests recorded in Reflect are automatically created as QMetry test cases, with unidirectional updates from Reflect reflected in the corresponding QMetry test cases.

Flexible Test Mapping: Map or unmap Reflect automated tests to existing QMetry test cases directly from the test details page or through a centralised mapping screen in Reflect, ensuring clear visibility and traceability.

Automated Suite Execution and Result Synchronisation: Executing Reflect test suites automatically creates corresponding QMetry Test Suites, links mapped test cases, and synchronises test execution results.

Unified Test Management and Reporting: QMetry acts as the system of record for both manual and automated testing. Reflect automated tests and suites are fully visible in QMetry, available for manual execution cycles, and supported by automation coverage reporting.

QA Teams: Scale automation while maintaining visibility and control within test management workflows.

Automation Engineers: Keep automated tests and execution results in sync with QMetry to reduce manual effort and operational overhead.

Test Managers and Leadership: Gain clearer visibility into execution status and automation coverage to support better decision-making.

Starting with QMetry v8.25, only custom fields that are enabled in projects for any work item type and explicitly selected by the System Administrator will sync to Custom Reporting. Additional fields must be enabled by the System Administrator upon request.

A new configuration screen under Integrations allows administrators to select the custom fields available for Custom Reporting. Previously, all custom fields were available in Advanced Query Reports by default.

This change improves the reliability of data synchronisation with the Custom Reporting database and prevents unnecessary syncing of unused fields.

For existing customers, any Jira or Azure custom fields currently used in Custom Gadgets will be automatically enabled to ensure existing reports continue to function. All other fields will be disabled by default.

The QMetry Help Guide for Cloud is now available at https://support.smartbear.com/qmetry-test-management-cloud/docs/?lang=en including “QI Search: Ask Me Anything,” now point to this new URL. Users should use this link for all future access to documentation.

A new Open API endpoint (POST /rest/requirements/latest/list) is now available to retrieve requirement data, including system fields, custom fields, synced Jira/Azure fields, and risk fields in the API response.

The Scheduled Report email template will no longer include an editable “From” field that allows users to enter an email address. Instead, the email body will automatically include the details of the user who scheduled the report dashboard. This change improves security by preventing modification of the “Scheduled By” information and misuse of the “From” field.

A compatible version of Automation Agent v8.25 is included with v8.25. The latest agent supports OpenJDK 25 only. Users currently using the agent must upgrade their JDK and Automation Agent as part of this release.

QMetry v8.25 upgrades all internally used third-party libraries to their latest versions, strengthening platform security and addressing known vulnerabilities.

Jira Integration now supports JQL queries of up to 2,000 characters when integrating Jira work item types with a QMetry project, increased from the previous limit of 500 characters.

Fixed a bug that caused the “Entity Key” filter on the Link Test Cases screen within Requirements to return no results when searching with a full Test Case key.

Fixed a bug that caused the "Executed At" column within the Test Case > "Test Executions" tab to be sorted incorrectly instead of in chronological order.

Fixed a bug that prevented list values from appearing in Multi Lookup custom fields when placed at the end of the System Fields section in the Test Suite “Add” layout via Layout Management.

Fixed a bug that caused Lookup and Cascading Lists to incorrectly show “No records available” in the Edit List screen, especially when list names included special characters.

Fixed a bug that caused slow load times in Test Executions when opening “Available Issue(s)” for issue/bug linking.

Fixed a bug that prevented Estimated Time from displaying for automated test cases imported via the Automation on the Test Execution screen.

Fixed a bug that caused some Azure DevOps fields to fail syncing in QMetry's Requirements and Issues modules.