Release Notes 8.25.x
Build 8.25.1 - Release Date: 2026-03-20
Improvements
QMetry Integration for Jira App Improvements
For Jira Cloud Customers (Connect on Forge Migration):
The QMetry Integration for Jira app has been migrated from Connect to Connect on Forge, aligning with Atlassian’s latest platform standards to enhance security, performance, and long-term support.
Core functionality remains unchanged, with improvements focused on user experience and UI:
Test Case Coverage:
Users can select and customise the visible columns for test cases and test steps (applies to the current view and resets upon tab change or data reload).
Test Case Executions:
Enhanced view with additional test run execution filters.
Added a dedicated filter to view executions linked to the currently selected defect.
Action Required - Upgrade Guidance:
QMetry SaaS US Customers (Using URL: https://testmanagement.qmetry.com/):
Jira admins must manually update the app.
Go to Manage Apps in Jira → Connected Apps → Installed Apps → QMetry Integration for Jira app → Click Upgrade.
For QMetry SaaS EU customers (Using URL: https://testmanagementeu.qmetry.com/):
Manual migration is required by Jira admins.
The QMetry EU Integration for Jira app is being replaced with the QMetry Integration for Jira app.
Go to Manage Apps → Connected Apps → Installed Apps → Uninstall the existing QMetry EU Integration for Jira app → Install the QMetry Integration for Jira app → Verify that the connection status is active under QMetry Configurations.
Important:
QMetry will continue to support existing versions of the Jira integration app for the next 2 months.
Upgrading at the earliest is recommended to avoid any disruption in Jira–QMetry synchronisation.
This update does not change existing data access permissions on the Atlassian end.
For Jira Data Center Customers (v11 Support):
Jira Data Center v11 Support: QMetry Integration for Jira App v2.4.0 now supports Jira Data Center 11.3.3 and is compatible with QMetry Cloud 8.25.1.
Auto-Generate Test Cases (AI Upgrade)
Auto-Generate Test Cases is now powered by the upgraded Llama 3 model, delivering more accurate and comprehensive test cases with improved understanding of requirements. The feature supports significantly larger requirement inputs (up to 8,000 words), resulting in better coverage and high-quality outputs.
Reference URL Attachments
Add reference URLs as attachments to Test Cases and Step Executions, enabling easy linking of external evidence (e.g., logs, cloud files, or documentation) without requiring local file uploads.
Bug Fixes
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.
Build 8.25.0.1 - Release Date: 2026-03-13
Bug Fixes
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.
Build 8.25.0 - Release Date: 2026-03-07
New Features
QMetry – Reflect Integration
Bridge the Gap Between Manual and Automated Testing
QMetry Test Management now integrates with Reflect to unify manual and automated testing workflows within a single system. This integration enables end-to-end management of automated web testing by synchronising automated tests, test suites, and execution results from Reflect into QMetry. By removing silos between automation and test management, QMetry serves as the single system of record for all testing activities.
Key Features
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.
Who Benefits:
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.
QMetry Insights – Admin Control for Jira/Azure Custom Fields
System Administrators can now control which Jira or Azure custom fields are available in QMetry Insight’s Visual and Advanced Query Reports, providing greater control over reporting fields.
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.
Miscellaneous Enhancements
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.
Bug Fixes
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.