| Column |
|---|
Description| Panel |
|---|
For Zephyr, To learn how to sync your requirements via the JIRA Requirements Sync feature within Zephyr system, please view the steps below. Terminology| Expand |
|---|
| title | Click to view more information on terminology regarding this page |
|---|
|
| Term | Descriptio |
|---|
| JIRA Requirements Sync | The ability to sync/import your requirements from JIRA utilizing a unique way of filtering via JQL and organizing your synced/imported requirements in folders dependent on fields. | | Top-Level Folder Name | The name of the folder that houses the synced/imported from the JIRA Requirements Sync feature. | | Field 1 & 2 | Individual fields that help organize the requirements synced/imported into folders. For example, field 1 could be "version" which would organize the requirements into folders depending on the version of the requirement. |
|
|
|
...
JIRA Requirements Synchronization
| Info |
|---|
In Release 6.2, it brings the release specific requirement tree structure which fixes JIRA sync limitation in 6.1.2 where: - If the same JQL is used in multiple releases of the same project, the requirement(s) and requirement tree auto changes will only get reflected to the latest release of a project.
Any JIRA sync that has the same JQL from any (different) releases of same project that is migrated from 6.1.2 over to 6.2 will need to have their JIRA sync re-created to utilize features from 6.2, so that it is able to maintain the same requirement(s) in the multiple requirement tree. Duplicate folders inside a parent requirement tree are not allowed. If an auto Jira Sync operation occurs, multiple folders with same name are created and they need to be deleted manually before a JIRA sync can be re-saved. |
1. Click on the 
button next to the release folder on the left-hand side.
...
| Note |
|---|
The older JQL search data remains as it is in the search result even if you change the JQL string for Jira Sync Config and even if it does not satisfy the current JQL.
The data gets removed if there is any update on the requirement via webhook call back. |
...