Version 11
This topic contains descriptions of new features and bug fixes for Zephyr Scale Server/Data Center. The most recent changes are listed at the top of the page.
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.
Bug fix:
You can no longer create a test case using the REST API without filling in all required custom fields.
Fixed the "Top 10 defects impacting testing" report. All Jira issues linked to a test case now appear correctly in the report.