Back to QMetry All Products Help Page
Release Notes
- Mrunalini Potnis
- Niharika Choudhury
- Rachit Kacheria (Unlicensed)
Build 8.20.0.3 - Release Date: 2025-06-02
Summary: Bug Fixes
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 > Users, role mapping section.
Build 8.20.0.2 - Release Date: 2025-04-25
Summary: Bug Fixes
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 prevented certain SAML users from generating test cases using QMetry Intelligence.
Build 8.20.0.1 - Release Date: 2025-04-21
Summary: Bug Fixes
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. 
Deprecation Notice: Rally Integration
As part of our commitment to delivering high-value features in QMetry, and based on current usage insights, Rally integration will be deprecated in the upcoming QMetry v8.21 release, scheduled for June 2025. The following changes will take effect:
The integration of Rally projects to sync work items as requirements and issues will discontinue. New Rally integrations will no longer be allowed. Existing Rally integrations will be disabled, and all related features will no longer be accessible.
This change will affect both QMetry SaaS and On-Premises customers. The Rally Integration features for SaaS environments will be discontinued with the release of version 8.21. On premise customers using QMetry version 8.20 (expected release in May) or earlier can continue to use the integration until they upgrade to version 8.21.
If your organization is impacted or is still using/planning to use the Rally integration, please create a support ticket with QMetry Support for further assistance
Build 8.20.0 - Release Date: 2025-03-29
Summary: New Features, Improvements and Enhancements
New Features
Enhanced Folder Selection
Users can now browse and select a folder directly on the creation screen when creating Requirements, Test Cases, and Test Suites. The folder path is now visible on the details screen, eliminating the need to hover over the folder breadcrumbs. Users can also move test assets between folders by updating the folder path directly on the details screen.
Key Improvements
Folder Selection for Cross-Functional Module Test Assets
This enhancement improves folder selection, particularly when creating test assets from cross-functional modules for the following operations. Previously, these operations autosaved such assets to the project's root folder, requiring manual relocation.
Creating a Test Case from a Requirement or an Exploratory Testing (ET) session.
Creating a Test Suite from a Requirement, Test Case, Requirement Folder, Test Case Folder or an Exploratory Testing (ET) session.
Creating a Requirement from an Issue.
Folder Selection for Auto-Generated Test Cases
Select the desired Test Case folder from the Details tab when auto-generating Test Cases using QMetry Intelligence (QI) from the Requirement and Test Case modules.
Folder Selection for Automation API Integration
Specify the Test Case folder path parameter to automatically organize newly created Test Cases into the desired folder when uploading automation results using the Automation API.
Improved Folder Navigation and Sharing
Users can now enjoy enhanced navigation and collaboration features with folders.
Clickable Folder Path: The folder path breadcrumb displayed at the top of the Requirement, Test Case, Test Suite, and Test Execution detail screen is now clickable. Each folder in the breadcrumb is interactive, enabling users to seamlessly navigate to the test asset list of the selected folder.
Folder Link Sharing: Users can easily copy a direct link to a folder by right-clicking on it or from the folder path breadcrumbs. Sharing this link allows others to directly access the specified folder within the folder tree structure, improving collaboration.
Enhancements to Auto Generation of Test Cases
Auto Test Case Generation (ATG) using QI is now Generally Available
The Auto Test Case Generation (ATG) AI feature has officially transitioned from Beta to General Availability (GA)!
ATG is an AI-powered feature designed to:
Generate test cases automatically based on requirements and user-provided descriptions.
Enhance existing test cases and steps to improve their quality and completeness.
Benefits:
Boost productivity by reducing the time and effort required to create comprehensive test cases.
Ensure thorough test coverage by generating test cases that effectively cover various scenarios.
Auto-Generate a Test Case Using an Existing Test Case as a Reference
QMetry Intelligence (QI) now allows testers to create or enhance test cases by leveraging any existing test case as a reference and applying user-provided instructions. QI generates test case and step details while retaining relevant information from the referenced test case, ensuring better test coverage and alignment with user-specified changes. This feature supports three key workflows:
Create a New Test Case - Generate a new test case using an existing one as a reference, incorporating the modifications specified by the tester.
Enhance an Existing Test Case - Use an existing test case from the project repository as a reference to update another existing test case by applying user instructions to modify its description and test scenarios while retaining relevant steps.
Improve Test Steps - Enhance existing test steps based on user-specified changes to ensure alignment with evolving testing objectives.
Enhancements to Test Steps View and Edit Experience
Persistent Step Number and Attachment Columns: The Step Number column is now locked and always visible, even when scrolling horizontally. This feature helps users accurately track the row they are editing, which minimizes errors and enhances efficiency. Additionally, the Step Attachment column is now permanently positioned next to the Step Number column, allowing quicker and easier access to view and edit attachments.
Improved Step Action Option Accessibility: The step edit and action gear buttons for inserting, deleting, duplicating, moving, or copying steps are now accessible at the right end of each step without requiring horizontal scrolling when multiple columns are present. The gear button appears upon hovering over the right end of the step row, enhancing usability and streamlining the editing process.
Full-Screen Step Editing: A new option to expand steps to full-screen is now available when editing test case steps. This feature allows users to maximize the step editor, using the entire screen for better visibility and an improved editing experience.
One-Click Column Name Expansion: The Step Table now has a new Expand Column button that allows users to view the full names of all field columns with a single click, eliminating the need for manual column expansion.
Security Enhancements
With release v8.20.0, the Tomcat version on the QMetry SaaS infrastructure has been upgraded to v10.1.39 to mitigate the Tomcat security vulnerability CVE-2025-24813.
Miscellaneous Enhancements
Users can now adjust column sizes to improve readability and usability across the following screens. Additionally, the newly introduced “Restore Width” option enables resetting columns to their default size.
Test Suite Screen: Linked Test Cases section on Creation and View Details screens.
Test Case Screen: Linked Requirements, Test Executions, and Issues sections.
Requirement Screen: Sections for Linked Test Cases and Issues.
Issue Screen: Sections for Linked Execution Runs and Requirements.
Bug Fixes
Fixed a bug that allowed test cases to be successfully imported via an Excel file without triggering a validation error, even when a mandatory field was left empty in the imported file.
Fixed a bug where the Status, Activity, and Module filters on the Scheduled Tasks screen displayed duplicate values.
Fixed a bug that prevented the auto-population of the test case and step details in the issue summary and description when creating an issue from the execution screen for test cases containing more than 50 steps.
Fixed a bug that prevented testers from executing test cases on the execution screen when accessing the test execution via a URL copied using the "Copy Link" feature.
Fixed a bug that prevented date-type custom fields from displaying on the detail screen when the section contained multiple date field.
Fixed a bug that prevented displaying custom fields with names containing the “Approval” keyword on the detail screen.
Fixed a bug that allowed users without the “customization” modify permissions in the target project to create custom fields when copying or moving test cases across projects.
Fixed a bug that prevented test step custom fields from being displayed on the execution screen for shareable test cases copied to another project.
Fixed a bug that prevented users from executing a copied test suite, even after linking it to a release and cycle, if the original test suite had no associated release or cycle.
Fixed a bug that displayed an incorrect count of associated projects for a custom field on the Manage Fields screen.
Fixed a bug where test cases did not appear in the Link Test Case section when filtered by folder while linking to a test suite. The issue occurred when renaming projects having over 1000 test case folders.
Fixed a bug that prevented test cases from appearing in the “Audit Log” report when a filter on “Approved Test Cases” was applied.
Fixed a bug that prevented SAML-authenticated users from downloading attachments linked to assets from the attachments tab of test assets.
Fixed a bug that prevented the complete Platform list from being displayed when creating a new test suite from the Requirements or Test Case from a new tab.
Fixed the download and open attachment icons across all modules to clearly distinguish between downloadable and URL-based (non-downloadable) attachments.
Fixed a bug that caused the Auto-Organize Requirements in Folders feature to stop syncing after mapping a new Jira issue type to the QMetry Requirements module.
Fixed a bug in Jira-integrated projects where the “linkedRqCount” column in the “issue” table within the Advanced Query Reports schema displayed an incorrect count.
Fixed a bug that allowed users without link permissions in the source project to link its test cases to a test suite in another project where they had link access. With this release, users must have the necessary link access in the source and destination projects to link test assets across projects.
Fixed a bug that prevented specific system gadgets, such as Planned vs Actual Executions and Test Suite Execution Summary, from retrieving and displaying relevant records when added to a custom dashboard due to folder filters not being auto-applied correctly.
Build 8.19.1 - Release Date: 2025-02-08
Improvements & Enhancements
Attachment Enhancements
Rich text fields now support adding inline images of up to 100 MBs.
A "Select from Linked Attachments" option has been added to the rich text editor under the Insert Image tool, enabling users to embed images directly from the attachments section of the test entity. Deleting the original image from the attachment section will make the embedded image unavailable.
A "Copy Link" option has been added for all files in the attachments section, allowing users to copy the URL of an image or file. This URL is intended solely for referencing files or images within the application's rich text editor. Deleting the original image or file from the attachment section will make its reference inaccessible.
Accessing non-image files added as attachments using URLs outside the QMetry application will require QMetry authentication for added security, except from within the integrated Jira.
Performance Improvements
Improved performance for loading issues synced from the Jira on the Issue List and Link Issues screens across the application.
Jira Integration Add-on Upgrade
Release v8.19.1 requires installation/upgrade of the QMetry-Jira Integration app to v2.3.2 for organizations using Jira 10 and v2.3.2_jira9 for organizations using Jira 9 or below. For customers utilizing Jira Cloud, the add-on will upgrade automatically.
Bug Fixes
Fixed a bug where cloned projects integrated with Jira failed to display newly added Jira custom fields or sync data updates after the original project was archived.
Fixed a bug where renaming a project with a large amount of data did not correctly change the root folder name for each module. This issue caused test cases to disappear from their folders, making them unsearchable when filtering by folder in the test suite and unavailable for linking.
Build 8.19.0.1 - Release Date: 2025-01-20
Summary: Bug Fixes
Fixed a bug that prevented assigning project access to read-only users and caused an exception.
Fixed a bug that prevented assigning project access to users created as read-only while converting them to regular users.
Build 8.19.0 - Release Date: 2025-01-04
Summary: Improvements & Bug Fixes
Permission Enhancements
'Release and Cycle' permissions have been introduced to control the creation, modification, archiving, and deletion of releases and cycles within a project. These permissions are now separate from the 'Modify' project permissions, offering more granular control over their management.
Users with 'Modify' permissions for test cases, requirements, or test suites can now archive their respective folders. Archiving folder permissions are now separated from 'Delete' and merged with 'Modify'.
Users with 'Execute' or 'Modify' permissions for Test Suites can now update the 'Execution Assignee' and 'Planned Date' for test case runs.
Execution Screen Enhancements
The test execution screen now displays the execution status for each group combination of a parameterized test case run, helping users quickly identify any combinations that have failed or remained unexecuted. This feature is available only for projects that have enabled the setting to derive the test case execution status from the statuses of its steps.
The Test Execution screen now shows the folder path for test cases, making it easier for users to identify them within a specific folder hierarchy. Users can sort the folder path, filter test cases, and view those belonging to a selected folder or its entire hierarchy. Additionally, the folder path column is now visible in the test case list view when linking test cases to the test suite.
Report Enhancements
A new 'Total API Utilization Report' has been introduced under the 'Login Summary Dashboard,' enabling administrators to track the daily and hourly allocation and consumption of Open API and Automation API requests.
Super Admins can now monitor API usage by setting up email alerts for daily or hourly Open API and Automation API requests when they near a defined threshold limit, helping to prevent overages.
Security Enhancements
Users now have the option to mask sensitive information, such as API keys and authorization tokens, in header values or the webhook body when creating or editing a CI/CD rule. These masked values will remain hidden in the user interface and cannot be retrieved, providing an added layer of protection for sensitive data.
The browser right-click options for image thumbnails and previews are now restricted to avoid unintentionally sharing URLs with unauthorized individuals.
Miscellaneous Enhancements
Navigating to the Projects menu now displays and highlights the currently logged-in project at the top of the list, making it more convenient for project administrators to access and manage settings.
The 'Projects' section in the QMetry menu is now called 'Project Management'. This change clarifies that all project setup tasks are managed within this section, making it easier for users to locate and carry out these actions. The former 'Project/Release/Cycle' menu has been renamed 'Projects'. A new sub-menu titled 'Releases & Cycles' has been added under 'Project Management' to give users easier access to the Release and Cycle management screens.
Jira Integration Add-on Upgrade
Release v8.19 requires installation/upgrade of the QMetry-Jira Integration app to v2.3.1 for organizations using Jira 10 and v2.3.1_jira9 for organizations using Jira 9 or below. For customers utilizing Jira Cloud, the add-on will upgrade automatically.
Bug Fixes
Fixed a bug that caused unarchived test cases to be displayed in the archived list when deleting test cases in bulk.
Fixed a bug that exported a blank data file using the 'export raw data' option from custom reports using inbuilt folder selection filters.
Fixed a bug that prevented the display of integrated Jira projects under the Project Integration section when syncing a QMetry project with multiple Jira projects.
Fixed a bug that prevented User Defined Fields (UDF) from appearing on the test execution screen's detail view for some cases.
Build 8.18.1 - Release Date: 2024-11-22
Summary: Bug Fixes
Fixed a bug where words in test case steps were split across lines in edit mode, impacting readability and editing.
Fixed a bug where selecting text in a test step caused it to become unselected and the text box to close abruptly in edit mode, disrupting the editing process and making text selection and modification difficult.
Fixed a bug that restricted the creation of users with email addresses and usernames containing an apostrophe ('), which also prevented sharing test assets with such users.
Fixed a bug that prevented users with test suite view-only permissions from seeing the 'Execute' button in the Test Suite's 'Test Executions' tab, which is needed to view the executions.
Fixed a bug that prevented the Jira fields section from loading into requirements in the cloned project if Jira integration was removed from the source project.
Fixed a bug that prevented non-admin users from setting build on the execution screen for dependent test cases until the execution screen page was refreshed manually.
Fixed a bug that prevented deleting custom dashboards with more than one gadget for certain cloud instances.
Compatibility
QMetry Jira Integration App v2.3.0 is compatible with Jira version 10.3.0 and QTM v8.18.1.
Build 8.18.0 - Release Date: 2024-10-26
Summary: New Features, Improvements & Bug Fixes
New Features
New AI Feature - QI Query Assistant (Currently in Beta, Only for Cloud)
Introducing the QI Query Assistant - a powerful AI feature that allows users to generate custom SQL reports directly from QMetry Insight using QMetry Intelligence (QI). The Query Assistant simplifies the reporting process, enabling users to create, modify, or understand SQL queries without requiring extensive SQL knowledge. The Query Assistant supports the following three use cases:
Generate a New Query - The QI Query generator creates SQL queries based on user-defined reporting needs expressed in simple English, aligned with the QMetry reports schema available in QMetry Insight.
Updating an Existing Query - The QI Query generator can help users modify existing SQL queries by adding fields and filters or implementing new logic and operators. To do this, users provide the existing SQL and clear instructions for the desired modifications in English. The output will be an updated custom SQL query reflecting these changes.
Explaining Query - The Query Assistant empowers users to understand SQL queries by providing explanations of their logic, tables and structure. This guidance enables users to comprehend the purpose and functionality of the query, aiding in debugging and troubleshooting.
Key Benefits: The classic advanced query custom reports feature requires users to manually write SQL queries based on the database schema, necessitating extensive SQL knowledge and an understanding of database tables and columns. Such requirements often lead to a reliance on technical teams and professional services. In contrast, QI empowers users with basic SQL knowledge to generate SQL queries quickly, significantly reducing the time and effort required.
Activation Instructions: To enable this feature, the QMetry Super Administrator must activate it by navigating to General Settings > AI Configurations.
How it Works: Upon activating the feature, users will see a new "QI View" under the Advanced Query Reports menu in QMetry Insights, alongside the existing Classic View. The QI View provides instructions and best practices for generating queries. Users can switch between the Classic SQL generation view and the QI View as needed.
Usage Statistics: System administrators can monitor the usage of the SQL generator feature for all users. Statistics for creating and updating reports using SQL queries generated by QI are accessible in General Settings > AI Configurations. Individual users can also view similar statistics tailored to their activities.
Identify QI-Generated Reports: Reports created using SQL queries generated using QI will display the QI logo when added to dashboards. The 'Custom Gadget' list view includes a 'QI generated' column to identify reports generated with SQL queries from QI.
Best Practices: All features operate according to the QMetry reports schema available in QMetry Insights. As a best practice, users must clearly describe their reporting needs in detail, specifying exact field names and any conditions or operations such as grouping, filtering, or sorting. The Query generator currently does not support the user-defined fields and works only with system fields.
New AI Features for Auto Generate Test Cases using QI (Currently in Beta, Only for Cloud)
Testers can now improve existing test case descriptions, pre-conditions, or step content using QMetry Intelligence (QI). For test steps, QI supports only the step description and expected outcome for content enhancement. Testers can enhance and refine the content using the following options, depending on their specific needs:
Regenerate Text: QI will rewrite the content for improved clarity or structure.
Suggest Alternatives: QI will provide alternative phrasing or wording options to enhance the content.
Add More Details to Text: QI will expand the content by including additional information or context.
Summarize Text: QI will condense the content into a shorter, more concise form while retaining key details.
Ask QI: Additionally, testers can prompt QI with specific commands such as Enrich Vocabulary, Adjust Tone (e.g. make it more formal or professional), Simplify Text, Proofread Text (e.g. check and correct grammar, spelling, and punctuation errors), Refine the Text or Make it More Engaging.
Note: This feature only generates text-based content. It will not retain any input that includes inline images, tables, URLs, or rich text data.
Testers can now generate or update all test steps on an existing test case using QMetry Intelligence (QI) based on the Test Case Summary and Description. Additionally, users can input a requirement or user-provided description, along with the test case description, to QI to generate test steps. This option allows testers to create test steps aligned with the scope outlined in the test case summary and description.
Direct Feedback: Testers can now share their improvement feedback from the QI interface about the generated test cases to help the QMetry product teams enhance the feature.
New Features for QMetry Jira Integration
QMetry now enhances security and streamlines authentication by supporting OAuth 2.0 for Jira Cloud and Jira Data Center integrations. This feature allows users to securely authorize QMetry to access Jira data without entering their credentials or API tokens, ensuring a more secure and compliant connection between the two tools. QMetry Admins can enable this optional extra security layer from the Integrations menu > Oauth settings to enhance authentication security with Jira. After this setting is enabled, users must authenticate their Jira accounts once using an OAuth verification token to create or update issues.
Release v8.18 requires installation/upgrade of the QMetry-Jira Integration app to version 2.2.9. For customers utilizing Jira Cloud, the add-on will upgrade automatically.
Improvements to Shareable Test Cases
Move shareable test cases, individually or in bulk, between folders within the same project or across different projects, just like regular test cases.
Copy shareable test cases, individually or in bulk, within the same project or across different projects, similar to regular test cases.
Import or re-import test cases that include linked shareable test cases using an Excel or CSV file. The shareable test cases must already exist in the projects, and the import file should contain the shareable test case key and the associated version to map during the import process.
Improvements to the Dashboards and Reports
Global filters are introduced on System and Custom dashboards, enabling users to view and apply common (i.e. shared) filters for all gadgets from the top of the dashboard. Instead of configuring filters for each gadget individually on a dashboard, users can now set shared global filters that apply simultaneously to all gadgets. Users still have the option to set specific and unique filters at the individual gadget level. When the global filters differ from those set on the gadget, an indication will be displayed, making it easier for users to identify discrepancies in the applied filters.
The Planned vs. Actual Execution gadget on the Test Execution Summary dashboard isenhanced to help QA teams monitor the progress of actual executions against planned dates.This improvement enables teams to assess current execution rates and determine therequired rates to meet delivery timelines based on the planned execution schedule.
All gadgets on the Test Execution Summary dashboard can now be filtered using Test Suite Folders.
Improvements to the Custom Reports
Pre-defined, ready-made browse folder filters for the Test Case, Test Suite, and Requirements modules are now available for users to add when creating custom reports using the Visual Reports or Advanced Query Reports modules.
The automation error messages and error trace fields for test step executions are available in the "teststepexecution" table within the Advanced Query Report module, enabling users to create custom reports using these fields.
Improvements to the Test Execution Screen
A new field, 'Planned Date,' has been introduced on the execution screen to help testers plan and track their assigned test case executions on specific dates. With both 'Planned' and 'Executed' dates now available, testers can easily monitor and compare their scheduled and actual execution timelines.
New options have been introduced on the Test Execution screen to export Test Executions and Test Cases with selected fields. Testers can export Test Executions including or excluding steps or Test Cases linked to those Test Executions with or without steps, depending on the fields they choose.
Two new duration fields, 'Automated TC Execution' and 'Automated Step Execution,' have been introduced on the execution screen to track the time taken for automated test cases and step executions, respectively. The durations are extracted and parsed from the automation result file uploads.
The 'Test Case Execution Time (Mins)' and 'Total Execution Time (Mins)' columns for automation executions on the Test Execution screen have been deprecated and will no longer store any values in the future.
The 'Test Case Estimated Time (mins)' column has been added to the Test Execution screen, enabling testers to easily view the estimated time for executing a test case.
Improvements to the Test Case Module
The option to 'Copy Steps from an Existing Test Case' has been introduced when creating or editing test case steps to enable testers to conveniently copy selected test steps from one test case to another within the same project or across different projects.
Improvements to Automation Agent
The Automation Agent now supports setting up recurring schedules for multiple test suite executions on the same agent, whether for the same test suite or different ones. When scheduling an execution command for an agent, all upcoming schedules for the agent are displayed, making it easier for testers to identify overlapping tasks. For multiple execution schedules set for the same time on the same agent, the agent will execute them sequentially on a first-come, first-served basis. The agent list screen now displays the total count of tasks 'Scheduled' and 'In Progress' for each agent.
New Features to User Provisioning through SCIM 2.0
The QMetry Administrator now has the option to allow QMetry to intelligently allocate and manage user license types from the IAM system when handling user provisioning using SCIM on the instance. In a QMetry instance with both Read-Only and Regular Licenses available:
Users with a Read-Only role across all projects will be automatically assigned/converted to a Read-Only License.
Users with a Non-Read-Only role in any project will be automatically assigned/converted to a Regular License.
When switching a user's license type from read-only to regular or vice versa, it's now optional to unassign the user from all groups if the user holds a Read-Only role across all projects. This rule applies when the user's license type is managed in the IAM system using the custom attribute 'QMetry_User_LicenseType'.
Bug Fixes
Fixed a bug that added an extra comma at the end of the last column for CSV exports of Requirements, Test Cases, Test Suites, Issues, and System and Custom reports.
Fixed bug that incorrectly displayed the 'Created By' field for the Azure work item created from within QMetry, showing the name of the user who configured the QMetry Azure integration instead of the user who created it.
Fixed a bug that prevented requirements import from Excel due to partially matching values encountered for the lookup list type field.
Fixed a bug that prevented viewing and downloading PDF and Word files containing an apostrophe (') or dash (-) in the file name.
Fixed a bug that caused an unsupported Jira team picker field type to appear in the integration field mapping configuration, allowing it to sync as both a requirement and issue field.
Fixed a bug that prevented test cases from being displayed as QI-generated after their details were updated, resulting in incorrect QI-generated statistics.
Fixed a bug that restricted the creation of users with email addresses containing an apostrophe ('), which also prevented sharing test assets with such users.
Fixed a bug that prevented assigning project and role for a user, along with user license type update from read-only to regular in the same operation.
Fixed a bug that allowed updating the actual outcome and execution status of testcases/steps for a closed test execution when the test execution was closed and another user had the same test execution session open.
Fixed a bug that prevented the execution of an advance query report using the DATE_SUB() function due to a parsing error in the WHERE clause.
Fixed a bug that prevented testers with execute permissions from adding comments for a testcase run in the Execution Detail View.
Fixed a bug that was causing inline attachments to not display in the descriptions of Requirements and Issues synced from Jira.
Fixed a bug that displayed a truncated summary for the shareable test case having a long summary when included in another test case.
Previous Versions
Back to QMetry All Products Help Page