Release Notes 8.22.x

From the Test Case module and Create Test Case screen:

From the Requirement module, while creating a test case:

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.

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.

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:

Requirement Details: Create test cases from the BDD section based on the feature file synced from the source code repository.

Test Case Module: Create test cases by importing feature files.

Test Case Details: Import individual scenarios directly into an existing test case.

Seamless import of Scenarios, Scenario Outlines, Examples, and Rules from feature files.

Automatically converts tags into Labels and assigns them to the corresponding test cases.

Use test case key tags to update existing test cases or create new versions and requirement key tags to link test cases to requirements.

Imports initiated from the Requirement or Test Case modules run in the background. Users can monitor the import progress and view detailed logs for failures or warnings.

Examples from Scenario Outlines are automatically created as test case parameters and grids, improving parameterized testing capabilities.

Seamless Integration Between Azure DevOps and QMetry: Supports real-time synchronization of Azure Work Items into QMetry as Requirements and Issues. Enable users to view Azure Work Item details within QMetry and create or update Azure Work Items, synced as Issues, directly from QMetry.

No QMetry License Required: Azure DevOps users can view QMetry test cases and execution details within Azure work items without requiring a QMetry license.

Free for Enterprise Customers: Available at no additional cost on the Azure Marketplace for QMetry Test Management Enterprise customers using Azure DevOps.

Granular Admin Control: Azure Project Administrators have the flexibility to enable or restrict QMetry test visibility for all or selected work items within their projects.

Cloud Support Only: The extension supports integration with Azure DevOps Cloud services only.

The Actual Execution Timer now supports incremental time tracking, allowing accurate measurement of total time spent across multiple sessions. Consolidated time is displayed when the timer is restarted and stopped.

The running timer is now pinned at the top of the screen, displaying the relevant Test Case Key under execution. Clicking the link navigates users directly to the corresponding test case execution run.

The Timer and Actual Execution Time fields now support the HH: MM: SS format, providing greater precision and improved control over time tracking.

The recorded time is now preserved during user actions such as page refresh, screen navigation, back button clicks, or closing and reopening the tab/window, ensuring continuous time tracking and preventing unintended time loss. When paused, the timer will display the paused time in a distinct color to indicate its status.

Project admins configure the recording of the actual execution time only through the timer, preventing users from entering it manually to streamline the process. Additionally, the project administrators can set up the timer to automatically start when testers begin execution of any step in a test case. The new settings are available under the customization - execution status section.

Folder Description Support - Add descriptions to folders to communicate their purpose and scope, improving organization and team collaboration.

Folder Operations Consolidated Under Right-Click Menu - All key folder operations are now accessible via the right-click menu, enhancing usability and improving navigation efficiency.

Introduced a new user-defined field type: Cascading Select List, allowing configuration of single-level parent-child dropdown values to support more structured and dynamic value entry.

Enabled the support for syncing Cascading Select List fields from Jira work items into QMetry Requirements or Issues, ensuring consistent field mapping across systems.

Exploratory Testing Extension Upgrade - Users must upgrade their QMetry Exploratory Testing browser extension to the latest version to get support for cascading field enhancements and comply with QTM release 8.22. The latest versions of extensions are as follows: Chrome 1.2.7, Firefox 1.1.1, and Edge 1.0.7.

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 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.

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.

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.

The Project Description field has been enhanced from a 255-character string to a large text field, allowing teams to enter more detailed project information.

A Description field has been introduced for Releases, allowing teams to provide detailed information for each release.

The Estimated Time field in test cases, along with the Actual Attended Time and Actual Setup Time fields in test executions, now support input in HH: MM: SS format, offering greater precision and control over time tracking. Previously, only minutes were supported, limiting time-tracking precision. After the upgrade, the previous saved values, which were in minutes, will be changed to the new format of HH: MM: SS.

Improved the filtering and dropdown selection menus to expand and utilize the available space when selecting filter options.

Enhanced Field Length Support

Improved performance when displaying Azure-synced issues on the Issue List and Link Issues screens.

Addressed multiple security vulnerabilities identified through routine internal audits and penetration testing to enhance overall application security and ensure compliance.

New Rally integrations are no longer supported.

Syncing Rally work items as requirements and issues is no longer supported.

All existing Rally integrations are disabled, and related features are no longer available.

This change applies to both QMetry SaaS and On-Premise deployments:For SaaS, Rally integration is discontinued from version 8.22 onward.

For On-Premises, customers on version 8.20 or earlier can continue to use the integration until they upgrade to v8.22.

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

Fixed a bug that caused certain 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 console logs were not being captured in the QMetry Exploratory Testing Plugin on the latest Chrome browser.

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

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

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 Jira issues from syncing and importing to QMetry due to changes in the underlying Jira API in Atlassian Jira Cloud.

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 caused test case imports to ignore relative folder paths and create test cases in incorrect locations.

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

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 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 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 intermittently exported dashboards in PDF format as blank.

Fixed a bug that caused certain Jira work items to fail to sync to QMetry due to special characters in a custom field of type Labels.

Fixed a bug where Jira Issues remained visible in the source QMetry project even after being moved to a different Jira project.

Fixed a bug that prevented certain users from navigating to the Execution screen or performing actions like approving or closing an execution due to missing default execution column view.

Fixed a bug that prevented users from deleting test cases linked to multiple test suites containing a higher count of test case executions.

Fixed a bug that prevents users from logging into QMetry using the 'Login with SAML' option with the Org Code generated in lowercase.

Fixed a bug that prevented the bulk moving of multiple test suite folders within a project.

Fixed a bug that caused the System Reports sub-menu to appear misaligned in collapsed mode, and the browser zoom was set below 100%.

Fixed a bug that prevented cloning the sample 'Health Tracker' project included with QMetry Cloud evaluation instances.

Fixed a bug that caused duplicate entries for the integrated Jira instance when a different Jira instance database was cloned or restored.

Fixed a bug where data in large text fields was not auto saved when clicking outside the textbox, requiring users to click Save.

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 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 prevented users with the necessary permissions from copying and moving test cases from the test case module list view.

Fixed a bug that prevented syncing updates for some users from Okta to QMetry via the Aquera app when SCIM was enabled.

Fixed a bug that prevented the creation and execution of advanced query reports using Common Table Expressions (CTEs) in the query editor.

Fixed a bug that prevented the deletion of a custom role, which appeared unassigned to any user but was still internally linked to users converted from regular to read-only access type and were previously assigned that role.

Fixed a bug where copying a test suite from within a folder incorrectly created the copy in the project root folder instead of the default destination path.

Fixed a bug that prevented updating the description for tabular gadgets added to dashboards.

Fixed a bug that prevented users from deleting test cases linked to multiple test suites having a large number of test executions.

Fixed a bug that prompted SAML users for re-authentication despite an active SSO session.

Fixed a bug that prompted SAML users for re-authentication despite not having reached the configured idle session timeout limit.

Fixed a bug that did not retain the saved changes when updating a user's role to "No access" under the Customization, role mapping section.