Version 12

The attachment precheck now flags a blocker when no attachment files are found on disk. Production migrations stop before export rather than proceeding without attachments.

The missing-attachment precheck warning now explains that the migration can proceed and that only the affected attachments will be skipped.

Test Cycles, Test Plans, and Test Executions without a key, and the entities that depend on them, are now skipped automatically instead of causing the migration to fail.

Export now tolerates inconsistent source data. Test execution steps without a source script ID, orphaned labels whose test cases no longer exist, and custom fields with a missing index are now handled gracefully, preventing the export from aborting.

Resolved an issue where migrated projects could end up with two default Test Case priorities, causing test case cloning to fail.

Resolved an issue where clicking an image in a step's Actual Result box jumped the editor to the next step and could clear entered content.

Resolved an issue where rich text attachments with special characters in the filename failed to render after a Jira Cloud Migration Assistant (JCMA) migration.

Resolved an issue where the "is related to" link to coverage issues was missing when creating a bug from a test execution in the new UI.

Resolved an issue where the Traceability panel failed to load when the Jira date and time format contained a Z timezone pattern.

Your data is now better protected when you use the private REST API. Requests containing an unknown trace link type no longer create unwanted trace link types in your instance.

Jira Cloud Migration Assistant (JCMA) enhancements:

Resolved an issue where the migration precheck for the last test results failed on Oracle databases and displayed the message "Something went wrong while correcting test execution last test result."

Resolved an issue where the Test Player showed an error page when a test case had a value in a select-list custom field with missing options. The Test Player now recovers and displays the value as empty. The same fix applies to test case grids and history comparison views.

Before you migrate to Zephyr Cloud using the Jira Cloud Migration Assistant (JCMA), the migration assistant now automatically detects and repairs several common data inconsistencies. These previously caused migration failures or required manual database intervention. They include:

Previously, the Traceability report failed when a Jira Query Language (JQL) filter matched more than 10,000 Jira issues. Results are now paginated correctly, so reports generate successfully for projects of this size and larger.

Resolved an issue where opening a test cycle from the Zephyr dashboard gadget and launching the Test Player showed an infinite "Loading Test Execution" screen. The Test Player now opens correctly regardless of the navigation path.

Resolved an issue where deleting a test execution status from a project's configuration caused any test cycle using that status to render blank. Missing statuses are now skipped instead of crashing the view.

Resolved an issue where grouping test cases by status in the Test Player on Data Center labeled all groups "Status unavailable." Status names such as Pass, Fail, and In Progress now display correctly.

Resolved an issue where the execution status field appeared empty when you opened the Test Player from a report, dashboard gadget, or execution history view. Status names now load correctly regardless of entry point.

Resolved an issue where the count badge on the Test Execution label did not update after you linked a Jira issue to a test step. The badge now updates immediately and stays consistent when you switch between the old and new user interfaces (UI).

Resolved an issue where pasting an image into a rich text field, such as Actual Results, could create a duplicate. This happened if you moved the cursor or scrolled before the upload finished. Only the correctly uploaded image now appears.

Resolved an issue where long Jira issue names linked to execution steps were truncated inconsistently. All linked issue names now display in a consistent layout, with a tooltip showing the full name on hover.

Resolved an issue where admin users received a 401 Unauthorized error when downloading attachments from test executions. Admins can now download these attachments.

POST /delete/testcycledeletion starts the deletion process.

GET /delete/testcycledeletion/status retrieves the status of the deletion process.

POST /delete/testcycledeletion/cancel cancels a deletion process that is currently running.

Project pickers in Zephyr now support search by project key, not just by name.

You can now enter more than 11 digits in a Number custom field.

The /testrun/{testRunKey}/testcase/{testCaseKey}/testresult endpoint now accepts an optional automated parameter (true or false). This parameter controls whether Zephyr classifies the execution as manual or automated in the application UI and reporting. The default is true, so Zephyr marks the execution as automated when you do not provide the parameter. To mark the execution as manual, set the parameter to false.

Jira Admins can now allow higher Data Center (DC) resource usage during Zephyr data migration to Cloud. This setting accelerates the JCMA migration export phase and is accessible only to Jira Admins. To configure the threshold, do the following:

Zephyr test entities on Jira work item traceability panels are now sorted alphabetically by project name, then by test entity key. This applies to the test case, cycle, plan, and execution sections. For example, AAA-T1AAA-T3BBB-T1CCC-T234, etc.

The Execution Details section of the Test Player now displays tooltips for values that are too long to display in full.

Fixed an issue where row numbers for execution steps displayed incorrectly when using test data in execution change history.

Fixed an issue with POST /testrun/{testRunKey}/testcase/{testCaseKey}/testresult where simultaneous calls to the endpoint created multiple last test results.

Fixed redirect issues related to the new test player that prevented the app from loading correctly.

Fixed an issue where Group by Status in the test player did not work correctly.

Fixed an issue where testers could not be assigned to test executions from the Test Cycle > Test Case tab.

Fixed an issue where users could not access the test player after navigating to a test cycle from a Zephyr dashboard gadget.

The hh:mm format now supports durations beyond the previous 99:59 limit, so you can log longer durations across the app.

In line with Atlassian's implementation, Zephyr no longer exports files larger than 250 MB during JCMA migration.

Files from previously failed migrations are now automatically removed at the start of a new migration run.

Resolved an issue with error messaging for attachment path conflicts. Following the folder structure change for attachment storage introduced in version 12.5 (/attachments/kanoahTests → .../attachments/kanoahTests/YYYY/MM), error messages are now clearer when a /YYYY directory already exists under .../kanoahTests.

Fixed an issue where navigating to a Zephyr test case by pasting its URL directly into the address bar resulted in an incorrect redirect.

Fixed an issue where test executions could not be updated when the same Jira work item was linked at both the test execution and test execution step level.

Enhanced the GET /testrun/{testRunKey}/testresults/page REST API endpoint with support for onlyLastExecutions filtering and totalCount in the response. Update your automation integrations before upgrading the plugin version.

Added the redesigned test player with an updated user interface, improved usability, bug fixes, and new capabilities. The Set all below to action now also updates the test execution steps to the selected status. You can still switch back to the legacy test player UI if needed.

Added support for listening to the TestCaseTraceabilityChangedEvent event when importing test cases linked to work items into Zephyr.

Added a new filter to the hasTestCoverage JQL function. The function now supports filtering by test case project. If no project is specified, the function searches across all accessible projects.

Fixed inconsistencies in the GET /testrun/ REST API endpoint when querying by project. The projectKey parameter is now accepted both with and without quotation marks.

Improved application stability and reduced performance impact on Jira nodes.

Fixed an issue that prevented some customers from cloning test cases.

Fixed an issue with test case export to PDF. Exported files now display correct values.

Added new endpoint for test case search POST /testcase/search. It now supports search by name or key.

Added new endpoint for linking test cases to Jira work items POST /testcase/link-issues.

Added new endpoint for creating test cases in bulk POST /testcase/bulk.

For more information, see the API documentation.

Updated JCMA to support compatibility with Atlassian Forge.

Fixed an issue where PUT /testrun/{testRunKey}/testcase/{testCaseKey}/testresult did not update test results correctly when test data was provided.

Resolved an issue with the test case import progress bar to ensure it shows accurate progress.

A new paginated Public REST API endpoint has been introduced: GET /testrun/{testRunKey}/testresults/page. This endpoint provides a paginated version of the existing: GET /testrun/{testRunKey}/testresults. Users are advised to update their automation workflows to use the new paginated endpoint. The non-paginated endpoint will be deprecated in a future release. For more information about this endpoint, see the API documentation.

When cloning test cases, you can now choose whether to include test case traceability links as part of the cloning process.

Resolved an issue where the Burn Down gadget did not load for users with their language set to German.

Improved the performance and reduced the memory usage of the hasTestResult JQL function.

Fixed an issue that caused users, groups, or roles to be added incorrectly multiple times to the permissions lists.