Release Notes 8.26.x
Build 8.26.0 - Release Date: 2026-06-20
Summary: New Features, Improvements, Bug Fixes
New Features
Test Run User-Defined Fields (UDFs)
QMetry now supports User-Defined Fields (UDFs) for Test Runs, enabling teams to capture, track, and report execution-specific metadata in a structured and consistent manner. Test Run UDFs are supported across execution management, reporting, automation integrations, and APIs, providing end-to-end visibility into execution data
Key Capabilities
Administrative Configuration: Administrators can define Test Run UDFs using the same configuration experience available for other QMetry modules. Only optional Test Run UDFs are supported in this release.
Execution Data Capture: A dedicated Test Run UDFs section is available on the Execution screen to view and update UDF values for individual test runs.
Advanced Filtering and Bulk Updates: Filter executions using Test Run UDFs and update UDF values across multiple test runs through bulk operations on the Execution screen.
QMetry Insights Reporting: Test Run UDFs are available in QMetry Insights, enabling teams to build custom gadgets and reports using execution-specific data.
Automation Integration Support: Automation APIs, as well as Jenkins and Maven add-ons, support Test Run UDFs during automated execution result imports. Test Run UDF values specified during import are applied consistently to all executions created as part of the automation run.
Test Suite Copy Enhancements: When copying a Test Suite, Test Run UDFs are copied along with executions. When using the Reset Execution Status to Not Run option, users can choose whether to retain or skip UDF values.
Open API Support: A new Open API endpoint, PUT /rest/execution/udf/bulkupdate, has been introduced to enable programmatic bulk updates of Test Run UDF values.
Requirement–Test Case Ordering Enhancements
Teams can now define and maintain the order of test cases linked to a requirement, ensuring coverage remains organised and consistent in Test Suites.
Flexible Reordering: Reorder linked test cases at any time to align with your specific execution or review workflow.
Automatic Sequence Management: Newly linked test cases are added to the end of the existing sequence. During initial linking, the order follows the sequence in which test cases are selected.
Seamless Test Suite Creation: When creating a Test Suite directly from a requirement, the defined test case order is preserved automatically to maintain traceability.
Test Case and Requirement Linking via Import
Users can now establish traceability relationships between requirements, test cases, and issues directly through CSV and XLS/XLSX imports, eliminating manual linking, reducing setup effort, and accelerating project onboarding.
Link Test Cases to Requirements: When importing test cases, link them to the latest version of requirements using QMetry Keys or External Keys provided in the import file.
Link Test Cases to Issues: When importing test cases, link them to issues using QMetry Keys or External Keys provided in the import file.
Link Requirements to Test Cases: When importing QMetry native requirements, link them to the latest version of test cases using QMetry Keys provided in the import file.
Shareable Test Case Linking Enhancements
Finding and linking shareable test cases is now faster and more efficient through enhanced filtering capabilities that reduce repetitive effort and improve discoverability.
Remember Last Used Filters: The Insert Shareable Test Case screen now retains and automatically applies the most recently used filters, making it faster to locate relevant test cases without configuring search criteria each time.
Filter shareable test cases by folder path to quickly discover and select relevant test cases within large folder hierarchies
New Open API for Jira/Azure Integration Instance Details
A new Open API endpoint, POST /rest/integration/instance/details, has been introduced to provide comprehensive, programmatic visibility into the Jira/Azure integrations configured for a QMetry project. This endpoint allows users to retrieve:
Mapped Jira instances associated with a QMetry project.
Jira/Azure projects integrated with a QMetry project for a specified Jira instance.
Detailed integration configurations, including mapped QMetry modules, Work Item Types, configured JQLs, field mappings, and other integration settings.
Jira Data Centre Integration Compatibility Update
To ensure compatibility with QMetry v8.26, customers using Jira Data Centre must upgrade the QMetry Integration for Jira app to v2.4.2. This version also adds support for Jira Data Centre v10.7.4.
What’s Coming in the Next Release (v8.27)
QMetry v8.27, planned for July, will focus on strengthening platform governance and expanding automation integration capabilities. Upcoming enhancements will introduce more granular administrative controls and greater flexibility for integrating automation frameworks through customizable import configurations.
Enhanced Granular Permissions
QMetry v8.27 will introduce enhanced granular permissions, enabling organisations to delegate administrative responsibilities with greater precision while maintaining stronger governance and tighter access controls across the platform.
Key Highlights:
Granular permissions for System Settings, Integration System, Automation, Customisation, and Open APIs.
Dedicated Automation permissions for Automation APIs, Automation Agents, and Automation Template Custom Parsers.
Independent Customisation permissions for Lists, Fields & Layout Management, and eSignature Settings.
Integration System permissions will be divided into dedicated permissions for managing Jira/Azure integrations with QMetry and configuring project-level integration mappings.
Independent Open API permissions enabling organisations to control API access with greater precision and security.
System Settings permissions will be split into multiple independent permissions, enabling separate control over AI Settings, General Settings & SMTP, Maintenance & Infrastructure, Identity & Provisioning, Administrative Controls, and access to Dashboards and Gadgets.
Custom Automation Import Templates
QMetry v8.27 will introduce Custom Automation Import Templates, enabling teams to import automation results from custom or proprietary XML report formats without requiring native integration support.
Users will be able to create reusable templates that map XML report elements to QMetry fields, giving teams greater control over how automation results are imported into QMetry. Templates will be managed at the instance level, reusable across projects, and supported through the Automation API, Jenkins, and Maven integrations.
Key Highlights:
Import automation results from custom and proprietary XML report formats.
Create and manage multiple templates for different automation frameworks and report structures.
Reuse templates across projects and automation pipelines.
Standardise automation result imports across teams and projects.
Extend automation support to frameworks and tools that are not natively integrated with QMetry.
The features listed above are planned for QMetry v8.27 and are subject to change.