| Redirect | ||||||
|---|---|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Tracking Requirements Across Zephyr and JIRA
Tracking Defects Across Zephyr and JIRA
Track Requirement, Test Case, and Defect Mapping Across Zephyr and JIRA
| Anchor | ||||
|---|---|---|---|---|
|
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.
Changes made to a specific fields for 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.
Anchor Anchor2 Anchor2
Tracking Defects Across Zephyr and JIRA
| Anchor2 | |
| Anchor2 |
Similar to requirements, Zephyr provides synchronization across both Zephyr and JIRA when tracking and updating your defects.
Zephyr will record any changes that occur to your defects from within JIRA and keep the updated record of the requirement across to your Zephyr instance.
To view the transparency for a defect between Zephyr and JIRA, use the following steps:
1. Navigate to the Defect Tracking page and search for an individual defect/bug using the filter options.
2. After searching for an individual defect/bug, click on the defect/bug ID using the ID column located on the left-hand side of the table view.
This will open up a new browser tab that launches your JIRA instance and will display the corresponding defect clicked.
- Users may need to log into their instance using their JIRA credentials to view the defect in JIRA.
Similar to requirements, changes made to a defect in JIRA or Zephyr will be updated and reflected on the other end.
For example, if we were to update the title (name) of a defect in JIRA, the defect 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 defect.
- Please view the two images below in a comparison to see the title has been updated across both Zephyr and JIRA.
Anchor Anchor3 Anchor3
Track Requirement, Test Case, and Defect Mapping Across Zephyr and JIRA
| Anchor3 | |
| Anchor3 |
Zephyr provides the synchronization of your requirements, test cases, and defects including the mapping between all three across Zephyr and JIRA. With the integration of JIRA to your Zephyr instance, we assure that Zephyr tracks the mapping and and related links between requirements, test cases, and defects.
For example, if we view an individual defect in the Defect Tracking page below, we can see that the defect is linked to specific test cases using the Test Case ID column. We can then click on the defect ID to take us to the defect in JIRA.
This will open up a new browser tab that launches your JIRA instance and will display the corresponding defect clicked.
- Users may need to log into their instance using their JIRA credentials to view the defect in JIRA.
- From here, we can see all the issues linked to this specific defect which displays the mapping of the defect to the test case issue.
If we click on any of the individual test cases in this section, it will navigate the user back to Zephyr and will display the test case that corresponds to the one clicked. This is extremely powerful to be able to view the transparency and mapping between your individual requirements, test cases, and defects through your usage of Zephyr and JIRA.
