Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Tracking Requirements Across Zephyr and JIRA

Zephyr provides users with the synchronization across both Zephyr and JIRA when tracking and updating your requirements. Prior to tracking and updating your requirements across both Zephyr and JIRA, JIRA needs to be connected to your Zephyr instance and users must set up a requirements sync with your JIRA instance. 

Zephyr will record any changes that occur to your requirements from within JIRA and keep the updated record of the requirement across to your Zephyr instance. This synchronization also works vice-versa. If there are changes made to a requirement in the Requirement Sync folder(s), then the changes made will be reflected in your JIRA instance as well as your Zephyr instance.

To view the transparency for a requirement between Zephyr and JIRA, use the following steps:

1. Navigate to your JIRA Requirements Sync folder and click on an individual requirement.

2. To view the transparency for your requirement from Zephyr to JIRA, click the "Go" link to navigate to the requirement in JIRA.

This will open up a new browser tab that launches your JIRA instance and will display the corresponding requirement clicked.

  • Users may need to log into their instance using their JIRA credentials to view the requirement in JIRA.

Any and all changes made to a requirement in either JIRA or Zephyr will be updated and reflected on the other end.

For example, if we were to update the title (name) of a requirement in JIRA, the requirement title would be updated in Zephyr.

  • In this scenario, the user must refresh the page in Zephyr to view the updated changes made to the requirement.
  • Please view the two images below in a comparison to see the title has been updated across both Zephyr and JIRA.

Tracking Defects Across Zephyr and Jira


Back to Top ^

Track Requirement, Test Case, and Defect Mapping Across Zephyr and Jira


Back to Top ^

  • No labels