Column | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description
|
...
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:
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....
3. Enter a JQL string to filter the requirements that you want to search and sync.
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 it does not satisfy the current JQL. |
4. Click "Search" to view the list of requirements.
...
Warning |
---|
Users have to re-sync their requirements if they were already using an existing query to setup their requirements via Epics and Sprints to properly display their epic and sprint folder structures. |
7. Click on the "Save" button after you've finalized your folder name, folder field filters, and you are satisfied with the requirements that you want to sync.
...