Release Notes 8.22.x

Build 8.22.1 - Release Date: 2025-09-04

Summary: New Features, Improvements and Bug Fixes

New Features

Test Case and Requirement Module

While creating test cases from the Requirement and Test Case modules, users can now plan and execute them within the same flow, enabling a streamlined end-to-end workflow.

With this feature, users can perform the following actions:

  • From the Test Case module and Create Test Case screen:

    • Link the test case to the requirements to establish traceability.

    • Link the test case to an existing Test Suite or create a new Test Suite for planning and execution.

    • New Test Suites created in this flow are automatically associated with the release and cycle defined in the originating test case.

  • From the Requirement module, while creating a test case:

    • Link the test case to an existing Test Suite, or create a new Test Suite for planning and execution.

    • The Test case and Test Suite created during the flow are automatically associated with the release and cycle defined in the originating requirement.

Once a Test Suite is created or linked, users can directly execute test cases within the same flow.

Key Benefits:

  • Unified end-to-end workflow from requirement → test case → execution → issues in a single flow.

  • Automatic association with release and cycle for traceability.

  • Reduced manual effort by eliminating cross-module navigation.

Jira Integration

Create Test Case and Test Suite options are introduced within the Jira Work Items and Test Case section. These options redirect users with authorised access to QMetry, allowing them to create test cases and test suites directly from Jira. This enhancement boosts productivity by reducing tool switching, simplifying navigation, and strengthening traceability between Jira and QMetry.

  • Create Test Case and Test Suite options are available for all work item types integrated with the QMetryRequirement module.

  • The Create Test Case option is available for all work item types integrated with the QMetry Issue module.

  • The created test case gets automatically linked to its originating work item. Similarly, the created test suite gets linked to all test cases associated with the originating requirement work item.

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

Azure DevOps Integration

  • Create Test Case and Test Suite options are introduced in Azure DevOps Work Items and QMetry Test Coverage. These options redirect users with authorised access to QMetry, allowing them to create test cases and test suites directly from Azure DevOps. This enhancement boosts productivity by reducing tool switching, simplifying navigation, and strengthening traceability between Azure DevOps and QMetry.

    • Create Test Case and Test Suite options are available for all work item types integrated with the QMetry Requirement module.

    • The Create Test Case option is available for all work item types integrated with the QMetryIssue module.

    • The created test case gets automatically linked to its originating work item. Similarly, the created test suite gets linked to all test cases associated with the originating requirement work item.

  • To ensure compatibility with QMetry Release v8.22.1, the QMetry Test Management Extension for Azure DevOps must be installed or upgraded to version 1.0.2

Bug Fixes

  • Fixed a bug that generated blank PDFs when exporting Custom and System Dashboards.

  • Fixed a bug that caused certain graphical charts or gadgets on the QMetry Custom Dashboard to display unrounded floating-point values instead of properly formatted two-decimal-place values.

  • Fixed a bug where filtering Jira issues by "Status" in QMetry for Jira-integrated projects returned empty results despite existing matches.

  • Fixed a bug where filtering requirements by “Created System” (QMetry or Jira) in the Requirements module returned no results.

  • Fixed a bug where console logs were not being captured in the QMetry Exploratory Testing Plugin on the latest Chrome browser.

  • Fixed a bug in Bulk Edit operations for test suites, where the "Skip Duplicate Linkage" option failed to prevent duplicate test case linkage to test suites.

  • Fixed a bug that caused requirement module to become unresponsive when users navigated from any module with Jira filters applied.

  • Fixed a bug where requirements synced from Jira were not auto-organized into the correct folder hierarchy in QMetry when the Fix Version was assigned via Jira automation.

  • Fixed a bug that caused users to encounter an error when setting execution status for test steps.

  • Fixed a bug that caused failures when uploading JUnit test result ZIP files through the Jenkins plugin with Automation Hierarchy 2, leading to unexpected errors and incorrect test case counts.

  • Fixed a bug that caused test case imports to ignore relative folder paths and create test cases in incorrect locations.

  • Fixed a bug that caused the Screens tab to freeze when exporting Exploratory sessions having more than 300 captures to PDF or Word.

  • Fixed a bug that prevented Jira issues from syncing and importing to QMetry due to changes in the underlying Jira API in Atlassian Jira Cloud.

  • Fixed a bug that prevented the "QMetryConfiguration" page from loading on Jira Cloud instances with a custom domain, which blocked the QMetry-Jira integration from establishing a connection.

Build 8.22.0.1 - Release Date: 2025-08-04

Summary: Bug Fixes

  • Fixed a bug that caused the Test Case module to become unresponsive in projects with a large volume of test assets.

  • Fixed a bug that caused the “Fetch List for Bulk Operation" API to return a 400 error when retrieving test cases for bulk operations.

  • Fixed a bug that caused an error when linking test cases via the “Link Test Cases from Requirement” option within the Test Suite module.

Build 8.22.0 - Release Date: 2025-08-02

New Features in Test Case Module

  • Test Cases Reusability Across Multiple Folders: A single test case can now be associated with multiple folders within the same project. This feature allows users to reference the same test case (identified by its unique key) across different folders, within the same hierarchy or across different hierarchies, without creating duplicates.

  • Folder-Level Test Case Sequencing: Users can now define a custom order for test cases within each folder. The sequence is maintained uniquely per folder, enabling teams to organize test cases according to specific scenarios or execution flows. The Order column appears in the test case grid only when Include Entities from Sub-Folder option is disabled.

Enhancements and Workflow Updates in the Test Case Module

The following workflow updates have been introduced in the Test Case module to enable test case reusability and folder-level sequencing. These enhancements simplify test case organization, enhance folder management and provide better control over archived assets.

  • The Project Root Folder now displays all active test cases by default. Any newly created test case will be saved under the “Project Root Folder”, in addition to the selected folder. The “Include Entities from Sub-Folder” view now applies only to subfolders and not to the Project Root Folder.

  • A new filter, Show Only Test Cases Not Assigned to Any Folder, has been added to enable users to quickly identify test cases that are not associated with any folder.

  • Archiving a test case now automatically removes it from all linked folders. These test cases are excluded from folder-level counts and no longer appear alongside active test cases. A new dedicated filter, Show Only Archived Test Cases, is introduced to enable users to locate and manage archived test cases. As part of this release, all previously archived test cases in the projects will be disassociated from their respective folders. For reference, the test case change log will record the original folder path.

  • Archiving a folder will now archive only the folder itself and not the test cases it contains. All test cases within the folder will be disassociated from it upon archiving. During folder archiving, users now have the option to move the test cases to another folder. If the test cases also need to be archived, they must be archived separately. A separate filter, Show Archived Folders, is introduced to enable users to view and manage archived folders.

  • The folder path navigation breadcrumbs at the top of the Test Case details screen now display the folder from which the test case is being accessed. This ensures accurate context when a test case is referenced across multiple folders. Sharing the link to the test case will open it from the Project Root Folder.

  • Deprecated Features:

    • Sorting by folder path is no longer supported across application screens, as test cases can now reside in multiple folders.

    • The test case count is no longer displayed next to the project root folder to prevent misrepresentation, as test cases can now reside in multiple folders.

Improvements and Changes to QMetry-Insights (Custom Reports)

Visual Reports Changes

  • The Test Case Entity table in Visual Reports now includes two new columns: Test Case Folder Name and Test Case Folder Archived, enabling users to generate reports based on folder names and easily filter out archived folders.

  • Action Required - Existing custom gadgets built using Visual Reports, having the Test Case Folder ID or Test Case Folder Path fields or filters, must be updated, as they will currently display incorrect data. To maintain accurate results, simply edit the gadget, remove these fields or filters, and re-add them to reflect the latest updates.

Advance Query Report Changes

  • A new table, testcasefolder, has been introduced to store test case folder information, including folder name, path, ID, and other related details.

  • Action Required - Existing custom SQL gadgets created using Advanced Query Reports that include the fields or filters “testcases.folderName”, “testcases.folderPath” , or “testcases.tcFolderID” should be updated, as they will currently display incorrect data. To maintain accurate results, update the queries to fetch or filter test case folder-related data by joining data from the new testcasefolder table.

Jira Integration Add-on Upgrade

  • As part of Release v8.22, compatibility requires upgrading the QMetry-Integration for Jira app to version v2.3.4 for customers using Jira 10, and to v2.3.4_jira9 for those using Jira 9 or earlier. For Jira Cloud customers, the app gets automatically upgraded.

Azure DevOps Integration Add-on Upgrade

  • As part of Release v8.22, the QMetry-Test Management Extension for Azure DevOps must be installed or upgraded to version 1.0.1 to ensure compatibility.

Miscellaneous Enhancements

  • The maximum field length for both Username and Alias is increased to 256 characters to support longer names.

  • The “Generate SQL reports” and “QI Search: Ask me Anything” AI features have officially transitioned from Beta to General Availability (GA)!

Bug Fixes

  • Fixed a bug that caused only the filtered labels to be exported when using the “Export All Records” option after applying a label filter in the Test Case module.

  • Fixed a bug that caused no results to be returned when applying filters in the Custom Shared Dashboard.

  • Fixed a bug that caused errors when uploading attachments with uppercase file extensions (e.g., .JPG, .PNG) in the attachments section.

  • Fixed a bug in the Test Suite module where the Test Cases tab showed a limited number of test cases due to fixed height not using full screen space.

  • Fixed a bug where the “Change Test Case Order” pop-up in the Test Suite module displayed fewer test cases due to a fixed height, despite available screen space.

  • Fixed a bug that caused the color modification option to be unavailable for Line charts in QMetry-Insights when configuring custom reports.

  • Fixed a bug where navigating into a test suite redirected users back to the test suite grid instead of the execution screen. 

  • Fixed a bug that generated blank PDFs when exporting Custom and System Dashboards.

Publication date: