Zephyr Known Issues

What do we define as a Known Issue:

Known Issues are product issues that we're aware of that may actively affect users using Zephyr. Not all issues are necessarily listed here. We characterize known issues from the following:

The issue is observed from multiple users and have generated a large number of support cases.
The issue affects or prevents the users of the system in using Zephyr.
An unexpected behavior that can be consistently reproduced.

Known issues are not issues regarding product outages and does not include feature requests or ideas.

For any additional assistance with any known issues that require guidance from our support team, please visit our support website and create a ticket for help.

Known Issues:

Issue	Summary	Planned to be fixed in next release	Internal reference
Crowd: Groups limited to 1000 users	When you are importing users specifically from Crowd and if the group in Crowd has more than 1000 users, only the first 1000 users will be imported.	No	ZEPHYR-26501
Test Step: Empty test step row created after saving any field while using rich text editor for test steps	When users are using the rich text editor for test steps and the user adds values to either the test step, test data, or expected results and then saves, a new empty row for the next test step is created. Typically, the new empty row for the next step is created only when the user finalizes creating the test step and clicks the add button or finishes filling in the expected result field.	No	ZEPHYR-26656
After enabling the Rich Text Editor, new line formatting in existing test steps are not retained	If the test step, test data, and/or expected results fields had formatting that included new lines, that formatting will not be retained after enabling the rich text editor, and those lines will be merged into a single line.	Yes	ZEPHYR-26735
When creating a defect in the Test Execution app, the remote link is not created in Jira	In 6.3, when users create a defect (specifically from the 'D' button in the test execution app), the defect is created properly, but the URL link back to Zephyr test execution is not added to the bug in Jira.	Yes	ZEPHYR-26966
Manual migration queries must be executed prior to upgrade for MS SQL customers	When users have duplicate test case versions within their Zephyr instance of 6.2 and plan to upgrade to 6.3, the upgrade process requires manual migration queries to be executed prior to running the upgrade script. This is done by our DevOps team for Cloud customers, but must be executed by customers with guidance from our support team for on-prem customers.	Yes	ZEPHYR-26717