Versions Compared

Old Version 30

changes.mady.by.user Marc Ray (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Kevin Pham

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel1
styleNone

Column

Description

Panel

For Zephyr Enterprise, To learn how to sync your requirements via the JIRA Requirements Sync feature within Zephyr Enterprise system, please view the steps below.

Terminology

Expand
titleClick to view more information on terminology regarding this page


TermDescriptio
JIRA Requirements SyncThe 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 NameThe name of the folder that houses the synced/imported from the JIRA Requirements Sync feature.
Field 1 & 2Individual 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.





Anchor
Anchor1
Anchor1

JIRA Requirements Synchronization

...

Info

 Prior to using JIRA Requirements Sync

Prior to using JIRA Requirements Sync, the user must be on the Requirements page within a specific project/release. There must also be a JIRA instance connected to this project and there must be existing requirements in JIRA for the connected JIRA instance.


Info

Release 6.2 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.

Scenario: You are a current user in Zephyr Enterprise. As a user in the system, you want to be able to sync your requirements from JIRA using the JIRA Requirements Sync feature on the Requirements page in the Zephyr Enterprise system.


1. Click on the  button next to the release folder on the left-hand side.

...

Scenario: You are a current user in Zephyr Enterprise. As a user in the system, you want to be able to view your recently synced requirements in the Zephyr Enterprise system.



1. Navigate through the newly created folder(s) to view your recently synced/imported requirements within the specific release.

...