Zephyr 6.6 Known Issues

Owned by Kevin Pham (Deactivated)
May 18, 2020
2 min read

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:

IssueSummaryPlanned to be fixed in next releaseInternal 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.

NoZEPHYR-26501
Test Step: Empty test step row created after saving any field while using rich text editor for test stepsWhen 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. NoZEPHYR-26656
Unable to post results through Vortex if user doesn’t have Test Repo/Test Planning accessFor users to be able to post results through Vortex (using zBot), they must have write permissions to the project’s Test Repository and Test Planning apps.YesZEPHYR-27989
Eggplant parser cannot be duplicatedDue to extra steps required to be performed for the EggPlant parser, these extra steps are hardcoded for the ‘EggPlant’ selection and are not available for an extra custom parser built by the user.NoZEPHYR-28274
Jira defects with ‘Team’ field cannot be updated from ZephyrDue to an existing issue with the Jira API (https://jira.atlassian.com/browse/JPOSERVER-2421), Jira defects that include the ‘Team’ field (from Jira Portfolio) can be created but cannot be edited directly from Zephyr.YesZEPHYR-28203