What's New
QMetry Test Management for Jira Server/Data Center v4.13.0
Dynamic Test Cycle Parameters in CI/CD Rule Triggers
QTM4J now supports the dynamic passing of test cycle parameters in CI/CD rule triggers.
Bulk Link of Multiple Jira Stories to Test Cases
QTM4J now allows bulk-select multiple Jira stories when linking test cases.
Amazon S3 as Attachment Storage
QTM4J now supports Amazon S3 as an optional storage solution for attachments.
Configurable Attachment Size Limit for Test Assets
QTM4J now allows Jira administrators to configure a maximum file size limit for attachments and inline images across test asset modules.
New Permission Scheme for CI/CD Rules
A dedicated CI/CD Rules permission scheme is now available to control access to the CI/CD Rules section in QMetry Automation.
Mandatory Bug Linking for Failed or Blocked Test Cases
QTM4J now enforces a mandatory "Link or Create Bug" prompt when marking test cases as "Failed" or "Blocked" to improve defect tracking and accountability.
Bypass Mandatory Fields for Skipped Test Cases
QTM4J now provides a "Skip Validation" option, allowing testers to mark test cases as "Skipped" and bypass mandatory fields.
Previous Versions
Test cases within a folder can now be arranged in a specific sequence using the drag and drop functionality.
Reordering for List Values
A new sorting option is now available for list values of Labels, Components, Status, Environment, Build, and Custom Fields.
Manage Test Cycles and Test Plans Visibility
Show or hide test cycles and test plans from subfolders in the parent folder.
Group and Sort in Execution List View
Save Filters for Executions
Users can save custom filter criteria on the Execution screen for future use.
Bulk Bugs Linking to Test Case Executions
Group Test Executions by Test Case Folder Sequence
Previous Versions
Enhance Your Jira Querying with QMetry JQL Functions
Introduced JQL functions offering enhanced flexibility and power for querying Jira stories and bugs linked to Test Cases, Test Cycles, and Test Executions.
Users can now reorder/move folders within the folder hierarchy using drag-and-drop across all modules.
A new 'Folder Order/Sorting' setting is now available under the Project Configuration. Project Administrators can enable custom folder ordering for the project, allowing teams to maintain a folder sequence that aligns with their testing workflow.
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.
Archive Test Cycle
Archive Test Plan
Archive test cycles and test plans before deletion to prevent accidental data loss.
Archive List Values for System and Custom Fields of Type "Lists" before Deletion.
All execution-related settings, such as Auto Update Execution Results, Execution Result Quick buttons, Managing Execution Results, Default Test Case Grid View Sorting/Grouping and new Timer Settings, are now merged under a single Execution Result menu, making it easier for project admins to manage them.
Permissions for Test Cycle Execution (test execution) and Managing Defects (linking, creating, and unlinking defects) are now separate, enhancing flexibility with more granular permission controls.
Project Administrators can now prevent testers from manually updating automated test case execution results.
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.
Stacked Bar Chart
Vertical Grouped Bar Chart
Tabular View
Introducing the QMetry Chart Macro - Confluence users can now seamlessly integrate live QMetry Reports into their Confluence pages.
The test case list view shows the count of comments, attachments, and stories associated with the latest version of the test case. Users can sort and filter on these counts.
Export complete test execution details in PDF and Word format for audit and compliance purposes. This export feature is available on the Test Cycle Execution screen.
Assignee will receive an email notification for test cases, test cycles, or executions when assigned individually or in bulk.
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.
Previous Versions
Introduced the 'Target vs Actual Execution' gadget within the Test Execution reports, empowering QA teams to monitor the current execution progress and comprehend the existing and necessary execution rates to meet delivery timelines. Generate the report in one of three modes based on the testing process followed by project teams.
Target Completion Date
Execution Velocity
Execution Planned Dates
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
Introduced date field 'Planned On' on the execution screen to enable testers to plan and track their assigned test executions on specific dates.
Grid View
List View
The Test Cycle's linked Test Case section displays test case custom fields along with the default system fields.
The Test Plan list view presents a consolidated execution summary of its associated test cycles.
The Test Plan's linked Test Cycle section displays test cycle custom fields along the default system fields.
Create an 'Ad Hoc' test cycle and perform executions for test cases directly from the Test Case Acceptance Criteria panel on the story page by specifying the desired environment, build, and assignee.
While executing the test cases from the story or the test case execution section, fill in the execution custom fields and the execution system fields, along with changing the execution status.
Import existing components from a Jira project into QTM4J components.
Introduced an option in the manage apps global settings that automatically consolidates all QMetry panels into a unified section, significantly enhancing the loading performance of the Jira Issue page.
Manage shareable test cases through a dedicated view within the test case module.
Create a shareable test case from an existing test case or independently from a dedicated new section. Additionally, shareable test cases can be versioned.
Insert shareable test cases as steps into another test case of the same or cross-project to reuse common steps.
Shareable test cases can include parameterized steps, and they will reference the parameter values from the test cases that reuse them.
Easily sync the latest version of the shared test case directly from within the associated test cases.
During test execution, the test case containing shareable steps displays the steps as usual, along with a reference to the shared test cases
Enable testers to conveniently copy test case steps from an existing test case while creating or modifying a test case, using the option "Copy steps from existing test case".
Copy and maintain the folder hierarchy of test cases when exporting them in bulk to other projects.
Search test cases within a project repository on specific keywords found within the description, pre-condition, and steps in addition to the summary.
Start New Execution in bulk for test cases on a selected environment.
The new 'Test Cycle Execution Summary' section on the Story page displays the test cycle details linked directly with the story and its execution summary, enabling better coverage and traceability.
Introduced the "Coverage by Test Cycle" report that displays the count and details of test cycles, both directly linked and not directly associated with the requirements.
