Release Notes

QMetry Test Management for Jira Cloud 4.14.3.1

Release Date: 2025-09-03

Bug Fix

• Fixed a bug where test result imports through Jenkins were failing due to using the HTTP protocol instead of HTTPS.

QMetry Test Management for Jira Cloud 4.14.3

Release Date: 2025-08-30

Summary: Enhancements and Bug Fixes

Enhancements

• Intellisearch now runs on our internal AI models, rather than ChatGPT. With this change, you no longer need to provide or
  manage external API keys — the feature works out of the box.

• Performance improvements and enhancements.

Bug Fixes

• Fixed a bug where Test Reports were exported with incorrect data.

• Fixed a bug where the “Executed On” field in the Test Case Execution Summary > By Time Frame report was displayed
  in the wrong order.

• Fixed a bug where Test Cycle Export fails in certain scenarios.

• Fixed a bug where the Export Report Open API does not dynamically refresh the date range for saved filters in the Time
  Frame report.

QMetry Test Management for Jira Cloud 4.14.2.1

Release Date: 2025-07-25

Summary: Enhancements and Bug Fixes

Enhancements

• Updated integration to use the latest Jira APIs, replacing a deprecated version. This change ensures long-term compatibility and stability.

Bug Fixes

• Fixed a bug where accessing drill-downs in the "Test Case Summary > By Custom Field" report caused a continuous loading spinner and unresponsive UI.

• Fixed a bug where defects created from the Test Execution screen were not being linked properly.

QMetry Test Management for Jira Cloud 4.14.2

Release Date: 2025-07-05

Summary: Improvements and Bug Fixes

Improvements

• AI-powered features are now generally available (GA) for all users. 

• Various internal optimizations to improve overall system performance.

Bug Fixes

• Fixed a bug where automation import error messages were not displayed under certain conditions.

• Fixed a bug where the execution result summary appeared incorrectly on the Test Cycle screen.

• Fixed a bug where the "Updated On" timestamp of the Test Plan was not refreshed when Test Cycles were linked.

• Fixed a bug where charts in the exported PDF reports displayed incorrect colors.

• Fixed a bug where the folder search did not return accurate results.

• Fixed a bug where Test Cycle execution results were not updated properly after unlinking test cases.

• Fixed a bug affecting background steps during Cucumber automation file uploads.

• Fixed a bug where the bulk selection and deselection functionality did not behave correctly.

QMetry Test Management for Jira Cloud 4.14.1

Release Date: 2025-05-17

Summary: Improvement and Performance Fixes

• QMetry Reports: Folder filter now supports = and != operators, resulting in better query performance and improved usability.

• Internal Performance Fixes: Various internal optimizations to improve overall system performance and responsiveness.

QMetry Test Management for Jira Cloud 4.14.0

Release Date: 2025-04-05

Summary: New Features, Enhancements, and Bug Fixes

New Features

Reorder Folders with Drag and Drop

Rearrange Folders using drag and drop functionality, maintaining a consistent order across all test management modules for improved organization and accessibility.

Reorder Test Cases within Folders
Test cases within a folder can now be arranged in a specific sequence using the drag and drop functionality. Each folder maintains a unique test case order, ensuring consistency across all test management modules and improving the test execution flow.

Export Test Executions to PDF and Word
Export Test Execution Details in PDF and Word formats, with an option to add custom logos via logo configuration.

Group Test Executions by Test Case Folder Sequence
Group Test executions based on the test case folder sequence, ensuring consistency with the test case module.

Enhancement
Display Parameter Combinations with Execution Status
Parameter value combinations will now be displayed with their execution status for the group, replacing the previously shown generic parameter combination.

Bug Fixes

• Fixed a bug where announcement banners obstructed the top test case in the Execution screen (List View).

• Fixed a bug where modifying custom field values after assigning them to test cases caused an error when drilling into the Custom Field Test Report.

• Fixed a bug where no warning or error message was displayed on the UI during test case import if the 'Summary' field in the Excel file was blank or empty for any test case.

• Fixed a bug where test case keys were displayed in an incorrect order when exporting Test Case reports.

QMetry Test Management for Jira Cloud 4.13.1

Release Date: 2025-03-15

Summary: New Features, Enhancements, and Bug Fixes

New Feature

Design Test Cycles with QI (Currently in Beta, Only for Cloud)

Introducing Design Test Cycles with QI, an AI-powered feature that transforms test cycle creation. QI analyzes your execution objectives to deliver precise recommendations for relevant test cases, ensuring thorough coverage and efficient planning. This feature empowers teams to enhance test coverage, speed up cycle creation, and manage complex testing across projects.

Key Features:

• AI-Powered Recommendations: Tailored test case suggestions aligned with your objectives.

• Cross-Project Search: Quickly find relevant test cases across multiple projects.

• Customizable Test Cycles: Control your test cycles through manual selection and automated sorting based on priority or QI recommendations.

Elevate your testing process today!

Watch Video: Create New Test Cycles

New Enhancements for Auto-Generate Test Cases using QI (Currently in Beta, Only for Cloud)

Enhance your testing process with QI-driven test case generation, enabling you to create comprehensive test cases more efficiently.

• By leveraging an existing test case as a reference and incorporating user-provided instructions, QI intelligently generates new test cases, ensuring improved test coverage and alignment with evolving requirements.

• Whether you need to create a new test case, update an existing one, or refine specific test steps, QI streamlines the process while preserving relevant details.

Bug Fixes

• Fixed a bug that prevented error logs from being displayed in a readable format for test cases uploaded via automation.

• Fixed a bug that added extra space to QMetry gadgets on the Jira dashboard when refreshed.

QMetry Test Management for Jira Cloud 4.13.0

Release Date: 2024-12-21

Summary: New Features, Enhancements, and Bug Fixes

New Feature

Display Theme for QTM4J
QTM4J now supports Dark, Light, and Match Browser themes, automatically aligning with Jira user preferences for a consistent experience. The dark theme enhances usability and comfort in low-light environments.

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 summary and expected results for content enhancement. Testers can enhance and refine the content using the following in-built 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 EnrichVocabulary, 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 generates text-based content only. It does not support or process input containing inline images, tables, URLs, rich text formatting, code blocks, certain ASCII characters, videos, or attachments.

Import Test Cases from Cucumber-Gherkins BDD Feature Files
Testers can now import functional test cases seamlessly from the Cucumber-Gherkins BDD feature. It saves significant time and effort, enabling teams to align their testing workflows with Agile and BDD practices. This feature is accessible from the following screens:

• Jira Requirement (Story) Page: Initiate test case creation from the BDD Panel using feature files synced from source code repositories or saved within the inbuilt BDD editor.

• Test Case Module: Import multiple feature files directly from the module.

• Test Case Details Page: Import individual scenarios within a test case as test steps.

Key capabilities include:

• Import Scenario, Scenario Outlines, Examples, and Rules seamlessly.

• Use test case key tags to update existing test cases or create a new version, and story key tags to link test cases with requirements.

• Automatically convert tags into Labels, assigning them to corresponding test cases.

• Utilize 'Examples' from scenario outlines as test case parameters.

• Imports initiated from the Requirement or Test Case modules run in the background. Testers can monitor the import status and access detailed logs to review failures or warnings.

Copy/Import QTM4J Project Setup
Jira Administrators can now simplify project setup by copying QTM4J Project Settings, Permissions, and Configurations from one project to multiple projects. Similarly, Project Administrators can import these settings from any project into the current project. This feature eliminates manual replication of settings, enabling administrators to use a project as a template.

• Administrators can choose to copy all settings or select specific configurations from the source project.

• The copy/import project settings process runs in the background. Administrators can access the status and detailed request logs to review failures or warnings.

• The copy process automatically skips duplicate fields and archived values, ensuring a clean and consistent configuration.

Offline Execution for Test Cycles
Testers can now execute test cases offline and upload the results to their respective test cycles. This feature enhances flexibility and productivity for teams working in environments with limited or no connectivity. Key highlights -

• Export Capability: Test cycles, with their associated test cases and steps, can be exported from the test cycle module to an Excel file for offline use.

• Offline Execution: Testers can update execution results and related test execution fields for both test cases and steps directly in the exported Excel file.

• Re-import Functionality: The updated Excel file can be re-imported to upload and update execution results and related details for test cases/step runs within the respective test cycle.

• The background process section will provide testers with any errors or warnings detected during the upload due to invalid or incorrect data. Audit logs will also record operations related to exporting and importing test cycles.

Archive Enhancements
Archive test cycles and test plans before deletion to prevent accidental data loss.

• Testers must archive test cycles or test plans before deleting them. Users with edit permissions can archive or unarchive them.

• Testers cannot modify the details of archived test cycles, their executions, or test plans.

• Testers can't import test executions for the archived test cycles and their executions.

• The archived test cycles or plans are not displayed on their list views and will be accessible through a dedicated view.

• Archived test cycles and their associated executions will appear with a grey background in the link section of the story, test plan or test case.

• Testers can generate reports to include or exclude archived test cycles and plans. Archived test cycles are tagged separately in the traceability report.

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 audit logs will not display the old and the new values in the rule history.

• Jira administrators can now control access to modify QTM4J project settings by assigning permissions to specific Jira groups. By default, users with Jira's Project Administrator and Browse Project permissions will continue to have access. These configurations are under the QTM4J Global Settings > General Configuration.

Bug Fixes

• Fixed a bug that prevented users from navigating to another test case through its URL inserted via the "Insert Link" option in the text editor within another test case.

• Fixed a bug that prevented uploading the JUnit test result automation file when the test case name attribute contained only numeric characters.

• Fixed a bug that prevented background colors from displaying for the test case, test cycle, and test plan workflow statuses in the Asset Macro table on Confluence pages.

• Fixed a bug that prevented error messages and failure logs from displaying for test case executions for JUnit and TestNG automation file imports uploaded via Automation Hierarchy 2 and 3.

• Fixed a bug that prevented displaying the correct latest test case execution result in the test case/acceptance criteria on the Story page.

QMetry Test Management for Jira Cloud 4.12.0.1

Release Date: 2024-10-21

Summary: Removed Feature from UI

• Removed the 'External System Import' option from the Configuration menu.

QMetry Test Management for Jira Cloud 4.12.0

Release Date: 2024-08-10

Summary: New Feature, Enhancements & Bug Fixes

New Feature in Automation

• Introduced parameter 'automationHierarchy' that provides flexibility in deciding the TestCycle - Test Case - Test Step hierarchy created for the automation result upload of TestNG and JUnit frameworks. The automation hierarchy can take values 1, 2, and 3, each with specific behavior tailored for different frameworks; more details are available on the Automation API page.

• Introduced parameter 'appendTestName' that enables easier identification of automation test cases once uploaded to QTM4J. This parameter applies only for TestNG and JUnit framework uploads with automation hierarchy as 2 and 3.

  • Teams utilizing the TestNG can choose to auto-append the Test Name before the Test Method Name to create QTM4J Test Case Summary during test results uploads. It makes it easier for testers to identify which test method belongs to which test while reviewing the TestNG results in QTM4J. 

  • Teams using the JUnit can choose to auto-append the Test Suite Name before the Test Case Name to create QTM4J Test Case Summary during test results uploads. It makes it easier for testers to identify the automated test case belonging to which test suite while reviewing the JUnit results in QTM4J. 

• Users with Jira's Administer Project permissions can configure the default behavior for 'automationHierarchy' and 'appendTestName' independently for TestNG and JUnit automation uploads using the newly introduced Settings under the Automation API page. Users can bypass these default settings by providing parameters externally through the automation API or plugins during the automation uploads.

• The latest release is compatible with Maven Plugin version 2.0.12, QMetry For Jira Test Management Plugin for Jenkins version 1.25, and QMetry for Bamboo DevOps/CD Plugin version 1.1.11. The support for 'automationHierarchy' and 'appendTestName' parameters is now available in the following versions of the external plugins.

New Features for Auto Generate Test Cases (QMetry Intelligence)

• Testers can now generate test steps using QMetry Intelligence (QI) based on the Test Case Summary and Description. Additionally, users can input a user story or user-provided description, along with the test case description, into 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.

• Usage Statistics: Testers and administrators can now view statistics on how the auto-generated test case feature is helping save time and effort for themselves and their project teams.

• QI Generated: Test cases created or updated using QI assistance are tagged as QI generated for easy identification and auditing. Testers can now filter test cases generated using QI assistance on the test case list screen. When testers do not select a folder during test case generation, the test cases are default tagged to the QI-generated folder.

• 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 in Administration

• Project Administrators, i.e. users with QTM4J configuration modification rights, can now copy custom fields along with their list values within the following scopes: 

  • Within the same project, i.e. from one module to another module.

  • Across the different projects, i.e. from a module in the source project to selected modules in the destination project.

• Jira Administrators can now modify or remove the default keyword "Cloned", added as a prefix to the test case and test cycle summary when cloning them within the same project or across different projects. This setting is available under QTM4J Global Settings.

• Introduced attachment storage consumption reports for Jira administrators to track current storage utilization by project and asset type. The report also tracks the cumulative storage utilization trend monthly for one year, helping administrators predict future storage needs.

Test Cycle and Test Execution Enhancements

• A timer (stopwatch) has been introduced on the execution screen for testers to automatically record the time spent executing a test case, enabling accurate measurement of the actual test execution duration.

  • When auto propagation of step execution results to the test case is enabled, the timer will automatically stop if a step fails or is blocked. The project admins can configure these auto-stop settings based on their project workflow. 

  • 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 a timer to automatically start when testers begin execution of any step in a test case. 

• Introduced date field 'Planned On' on the execution screen to enable testers to plan and track their assigned test executions on specific dates. The 'Planned On' and 'Executed On' dates now allow them to monitor both their planned and actual executions. The Test Case Execution reports can now be filtered based on the 'Planned on' date. 

• While cloning test cases individually or in bulk, testers can now choose to retain the linkage with associated stories, which helps maintain traceability.

• While creating a new version of the test case, testers can now choose to copy the linkages with associated stories from the previous version.

• While creating a test cycle and selecting test cases, testers can now hide already linked testcases from the selection list. It simplifies filtering and choosing test cases from multiple folders.

• The Status field can now be updated inline for Test Cases, Test Cycles, and Test Plans directly from the list and link screens, allowing users to quickly update the status of test assets without opening the detailed view for each item, improving efficiency.

• Testers can now inline-edit the Execution Assignee, Environment, Build, Planned On Date, and Actual Time fields for the most recent test case run directly from the List View on the Execution Screen.

• The Estimated Time on the Test Case details screen and the Actual Execution Time on the execution screen now accept time in the HH: MM: SS format, enabling testers to record both estimate and actual time more precisely, down to the second.

Report Enhancements

• The graphical charts in the report are now accompanied by a tabular view, presenting a summary of counts and percentages to enhance the user viewing experience.

• The "Target vs. Actual Execution" gadget in the Test Execution report is now enhanced to empower QA teams to monitor current execution progress and understand the existing &determined test execution rates needed to meet delivery timelines based on the planned execution dates.

Performance and Usability Enhancements 

• The project selection list now lets testers display only QMetry-enabled projects and mark projects as favorites, making searching easier.

• All execution-related settings, such as Auto Update Execution Results, Execution Result Quick buttons, Managing Execution Results, and new Timer Settings, are now merged under a single Execution Result menu, making it easier for admins to manage them. 

• The QMetry menu has been revamped to enhance performance, with project selection now visible above the menu items and consistently applied across both the module and configuration screens. The menu icons are introduced, which enable users to collapse the menu while accessing its options.

• User preferences for expanding nd collapsing the folder tree menu are now preserved, which leads to improved performance when loading module screens.

Bug Fixes

• Fixed a bug that led to an incorrect calculation of consolidated actual time for the test cycle when updating the actual time for individual test cases using bulk operations.

• Fixed a bug that allowed the creation of test assets for deleted Jira projects using API.

• Fixed a bug that prevented the export of test case runs from the execution screen to an Excel file from a project with more than 100 custom fields. 

• Fixed a bug that prevented users from correctly navigating to the relevant test case and test cycle details from the test execution status or assignee update email notifications.

• Fixed a bug that prevented uploading automation result files using Maven and Bamboo plugins when test case, cycle, or execution fields contained values with acute accent characters. This fix is part of Maven v2.0.12 and Bamboo Plugin v1.1.11. 

• Fixed a bug that displayed an incorrect error message when cloning more than the allowed number of test cycles using the Open API.

• Fixed bug that prevented bulk updating executions when filtered based on custom fields and selected using the 'Across All Pages' option.

• Fixed bug that prevented assigning test case type as automated or manual when creating or updating test cases using the Open API.

QMetry Test Management for Jira Cloud 4.11.2

Release Date: 2024-06-26

Summary: New Feature & Bug Fix

New Feature

• Custom field type 'Multi-Line Text Box' supports rich text editing.

Bug Fix

• Fixed a bug that incorrectly imported execution attachments during the upload of cucumber automation results.

QMetry Test Management for Jira Cloud 4.11.1

Release Date: 2024-05-25

Data Residency Support in Australia

QTM4J now supports data residency in Australia for new cloud installations only. This means that if your Jira product location is pinned to the Australia region, any new installation or reinstallation of the QTM4J app will occur there. With this enhancement, Jira Admins can ensure that QTM4J’s user-generated content is stored within Australia, giving them greater control over their organization's data. For companies in regulated industries such as finance, government, or healthcare, data residency is crucial for operating in a cloud environment.

Please note that for existing customers, the migration of QTM4J data to the Australian region is not yet available or supported. However, this feature will be rolled out soon. If you have any questions or need assistance, please don't hesitate to reach out to our support team.

QMetry Test Management for Jira Cloud 4.11.0

Release Date: 2024-05-11

Summary: New Feature, Enhancements & Bug Fixes

New Features
Report Enhancements

• Introduced a new category of custom reports empowering users to generate two-dimensional or single-dimensional gadgets for all the modules. These gadgets offer multiple viewing options, such as stacked bars, vertical grouped bars, and tabular views, with the drill-down option to slice and dice data for analysis.

• Revamped the QTM4J reports to enhance the elegance and visual appeal of the graphical charts within the gadgets. The counts, percentages, and legends displayed on the gadgets are now consistently visible, eliminating the need for hovering.

• All the Test Case Execution Summary reports now show the total count of records for every column in the tabular chart.

• More export choices -

  • Export the graphical images in PNG, JPEG, PDF, and SVG formats.

  • Export the tabular summary view of the report in CSV format.

  • Export all the traceability reports in PDF and Word format.

• Improved Export Experience -

  • Download the Excel export of reports with large datasets directly from the notification sections instead of from an email sent containing the download link.

  • Track the progress of the report exports conveniently accessible from the background process notification section.

Confluence Integration Enhancements

• Introducing the QMetry Chart Macro - Confluence users can now seamlessly integrate liveQMetry Reports into their Confluence pages. This macro empowers users to:

  • Embed dynamic QMetry report gadgets into the Confluence page for reporting purposes.

  • Drill down into graphical charts to view and export filtered records in Excel.

  • Export graphical images in PNG, JPEG, PDF, and SVG formats for sharing.

• Export confluence pages containing QMetry Asset Macros to PDF and Word formats.

Audit Log Enhancements

• Audit logs now record the delete, import, and export operations on the test cases, test cycles, test plans, and executions to trace the details of the users who performed the actions. Moreover, the audit logs also record the create, delete, update, move, and copy operations on test cases, test cycles, and test plan folders.

Bug Fixes

• Fixed a bug that required users to scroll to the left end of the screen to click the expand button and view the full text of the test case precondition on the execution screen.

• Fixed a bug that prevented the users from auto-generating test cases using the QMetryIntelligence feature on the Firefox browser.

• Fixed bug that prevented the applied filters on reports from working correctly for users having language set as Spanish.

• Fixed a bug that did not display hyperlinks on defect keys for all the Test Case execution reports.

• Fixed a bug that prevented uploading the TestNG results when the test tags in the result file contained multiple classes.

• Fixed a bug that prevented QMetry sections from displaying on the issue page when the first project is not QMetry enabled.

• Fixed a bug that prevented displaying accurate time for all the events per daylight-saving time standards.

QMetry Test Management for Jira Cloud 4.10.2

Release Date: 2024-03-23

Summary: New Feature & Improvement

New Feature

• Introduced an option in the Manage Apps global settings that automatically consolidates all QMetry panels into a unified section, thereby enhancing the loading performance of the Jira Issue page.

Improvement

• Enhanced performance during the loading of Test Case and Test Cycle modules.

QMetry Test Management for Jira Cloud 4.10.1

Release Date: 2024-02-17

Summary: New Feature

• Auto-Generate Test Case using QMetry Intelligence (Currently in Beta):
  Testers can now auto-generate functional test cases using QMetry Intelligence (QI) directly from the Story Page or the Test Case Module. Furthermore, testers can utilize QI to generate the test case description, pre-condition, and test steps in an existing test case, with options to either update the existing version or create a new version.
  Key Benefits:
  The auto-generation feature aims to expedite the test case authoring phase by quickly creating test cases with steps aligned with specified requirements. As a result, it effectively reduces the manual efforts required by testers, allowing them to focus more on test case execution and validation. This enhancement ultimately saves valuable time during the testing lifecycle.
  How It Works:
  The QI model extracts relevant details from either the story description or the user-provided description to generate modular functional test cases with adequate coverage, ensuring thorough validation of the acceptance criteria for the story. Testers can accept, modify, or reject the generated test cases before approving them for creation into the test case library. For optimal results, the story description must be clear and well-structured.
  Activation Instructions:
  To activate the 'Generate Test Cases with QI' feature for all QMetry users in QMetry-enabled projects, the Jira super administrator must enable it for the Jira instance

QMetry Test Management for Jira Cloud 4.10.0.1

Release Date: 2024-01-31

Summary: Bug Fix

• Internal bug fix.

QMetry Test Management for Jira Cloud 4.10.0

Release Date: 2024-01-20

Summary: New Features & Bug Fix

New Features

Automation Enhancements

• Introduced parameter "matchTestSteps" that allows reusing an existing test case version without matching its test steps and importing only the test case execution status for the automation result uploads of JUnit, TestNG, and Cucumber frameworks.

• The automation upload of Cucumber test results is enhanced to allow the import of the screenshots/images contained as part of the step execution under the after-tag. •

• The latest QTM4J release, version 4.10.0, is compatible with Maven Plugin version 2.0.10, QMetry For Jira Test Management Plugin for Jenkins version 1.22, and QMetry for Bamboo –DevOps/CD Plugin version 1.1.8.

Report Enhancements

• Introduced the 'Target vs Actual Execution' gadget under the Test Execution reports, allowing QA managers to comprehend the current and expected execution rates to meet delivery timelines.

• The graphical charts in the report are now accompanied by a tabular view, presenting a summary of counts and percentages to enhance the user viewing experience.

• The tabular graph of all reports now displays only the selected columns as applied in the filters.

Administrative Enhancements

• Make system and custom fields mandatory/optional for test cases, test cycles, test executions, and test plans based on the project workflow.

Test Cycle and Test Execution Enhancements

• The Test Cycle's linked Test Case section displays test case custom fields along with the default system fields. Users can show/hide, rearrange & filter these fields based on their viewing preferences.

• View & Update execution system and custom field values when executing test cases directly from the Story as well as the Test case's execution tab.

Test Plan Enhancements

• The Test Plan list view presents a consolidated execution summary of the associated test cycles.