A Zephyr project integrated with a Jira instance couldn’t be updated or deleted if the Jira instance was down. (ZEPHYR-29276, ZEPHYR-30567)
If an SSO user was logged out both from Zephyr and from Okta, clicking a link in the Issues Links section of a Jira issue opened the Release Summary page instead of the Test Execution page. (ZEPHYR-29390)
An error occurred when trying to update both the Status and Resolution field values of a Jira defect in Zephyr. (ZEPHYR-30080)
Issues moved between sprints in Jira were not reflected in Zephyr. (ZEPHYR-30091)
Sometimes, a wrong sprint value was shown in issue details in Zephyr, and no sprint value was shown in the Update Defect dialog. (ZEPHYR-30092)
No error message was shown when a user tried to bulk update defects belonging to different projects. (ZEPHYR-14552)
Selecting a defect in the list of defects unselected the defects selected on the previous page of the list. (ZEPHYR-18195)
The Filed by value was changed to the user who updated the defect. (ZEPHYR-30033)
Only 5000 rows of data were exported to an audit log even if the fetched data was more than 5000 rows. (ZEPHYR-29418)
Sometimes, audit logs exported to a CSV file contained more records than expected. (ZEPHYR-29880)
The logout event was not added to the audit log if the user session had timed out. (ZEPHYR-30329)
Fixed incorrect time stamps in exported files. (ZEPHYR-30129)
If a test case was updated after being executed, the data of the previous test case version was replaced with the new data. (ZEPHYR-30338)
Three-digit test step numbers were wrapped on the Test Repository page. (ZEPHYR-30575)
An error occurred when trying to synchronize a sub-folder that had been deleted from the Test Repository page. (ZEPHYR-29355)
A wrong link to the Zephyr login page was sent to newly created SSO users. (ZEPHYR-29805)
Sometimes, an error occurred when testing an SMTP connection. This happened because TLS 1.2 was not supported. (ZEPHYR-30535)
An improper redirect URL was used when connecting to Zephyr via Okta SSO. (ZEPHYR-29838)
Files attached to a test case created via API couldn’t be viewed in Zephyr running in a cluster environment. (ZEPHYR-29984)
Sometimes, an error occurred when several users tried to update the same project by using API. (ZEPHYR-30482)
During Zephyr installation, Windows Defender marked some Zephyr files as malware. (ZEPHYR-29985)
In Bamboo with the Zephyr Enterprise Test Management Add-on installed, updated task data was not retained. (ZEPHYR-30010)
The Attachment field has been removed from the list of Zephyr fields on the Requirements > Import > Import Requirements page, as attachments cannot be imported. (ZEPHYR-30064)
When an automated test started, its status was changed to Not Executed instead of WIP. (ZEPHYR-30201)
The status of automated tests was changed automatically after the test execution. Now it remains WIP until you change it manually. (ZEPHYR-30463)
A traceability report couldn’t be downloaded if requirements had a lot of test cases mapped to them. (ZEPHYR-30350)
The warning message that appeared when deleting a group was unclear. (ZEPHYR-30467)