Version 11

This topic describes new features and bug fixes for Zephyr Scale Server/Data Center. The most recent changes are listed at the top of the page.

11.5 - August 21, 2025

Bug fixes:

Resolved an issue where test executions lasting more than 24 hours were blocking updates to key fields like Status, Executed By, and Actual Time. These fields now update correctly, even when execution time exceeds 24 hours.
Fixed a problem with the traceability panel in Jira issues that was not functioning properly for some users.

Improvement

Enhanced the Import from Other Project feature: You can now import test cases that include required custom fields, provided those fields have matching names, types, and option values in both the source and target projects.

11.4 - August 5, 2025

Bug fixes:

Resolved an issue that prevented test case attachments from being imported correctly when using the Import from other Projects feature.
Resolved a 500 error in the Update Test Execution API (PUT /testrun/{testRunKey}/testcase/{testCaseKey}/testresult) that occurred when the request included an unset Date Picker custom field. This issue typically affected new or cloned Test Cycles.
Fixed an issue in the Update Test Execution API (PUT /testrun/{testRunKey}/testcase/{testCaseKey}/testresult) that caused a 500 error when updating test results containing data-driven steps. The API now handles data-driven test results without errors.

11.3 - July 22, 2025

Improvement:

You can now use Jira user names in user picker fields when importing test cases from CSV files. Jira user IDs are still supported.

11.2.1 - June 16, 2025

Bug fix:

Formatted text and attachments in rich text fields now show up correctly when exporting test cases to PDF.

Improvement:

Added a permission check for importing test cases from CSV. To create new custom field options during import, you now need the “Configuration → Configure” permission in Zephyr. This requirement applies to multi-choice and single-choice custom field types. If the permission system is turned off, the check does not apply.

11.2 - May 21, 2025

In this update, the following bugs are resolved to enhance the overall functionality of the system.

Bug fixes:

Resolved an issue that allowed test cases to be updated through PUT /testcase/{testCaseKey) without including the required custom fields.
Resolved an issue where the "test execution change history" was not generating accurately when Jira's system language was set to German.
We resolved an issue with the Coverage (Issues) filter not working Test Case tab.
Zephyr no longer breaks the Jira header colour.

Improvement:

We have added a new issueLinks field to the request body of POST /testrun. This new field works like issueKey but allows you to link multiple Jira issues to a test run at once. The existing issueKey field is deprecated. We recommend switching to issueLinks as soon as possible.
We have added a new issueLinks field to the response body of GET /testrun/{testRunKey}. This new field works like issueKey but returns all Jira issues that are linked to a test run. The existing issueKey is still visible in the response, but it will be removed in a future release.

11.0 - April 2, 2025

Zephyr Scale is now simply called "Zephyr" —delivering the same high-performance test management you trust, just with a new name.

Nothing changes about how you use Zephyr in your Data Center environment. You will continue to enjoy robust test planning, execution, and reporting—all within Jira, but Zephyr Scale will now be called just "Zephyr" in-product, our documentation, and in your billing and subscription details.