Forum Discussion

stelee582's avatar
stelee582
Regular Visitor
2 months ago

Sync Jira Requirements to ZE

I'm trying to sync my Jira Requirements to Zephyr Enterprise.

I only want to have 1 version of each Jira ticket in ZE. Right or wrong, my team tends to change the Fix Version of our Jira tickets often. For our purposes, Jira's "Fix Version" and ZE's "Release Version" are the same (even though for some reason ZE's "Release Version" apparently will not map to Jira's "Fix Version"). I need to be able to "move" Requirements around the Releases and ZE doesn't really want to do this. So basically, I want all Requirements imported from Jira to 'live' at the project level (i.e. "Project Requirements") so I can then allocate/deallocate as needed without loosing my test case mapping and without creating multiple version of the same Requirement. 

I see two options for importing Requirements...

  1. Import Requirements
  2. Jira Sync Config

If I use "Import Requirements" and specify a JQL or a Jira filter, and also select "Fix Version/s" and "Issue Type" as my Field 1 & Field 2, the resulting import is placed in the "Imported" folder with the structure I want. I can them move the imported filter to "Project Requirements" and allocate tickets to each release as-needed.

When starting the Import there is a message on the popup saying...

"Folder structure will be created at the time of importing requirements from JIRA. Thereafter, the content of the imported requirements will be in sync with JIRA changes, but the folder structure will not be dynamically adopted. For complete sync, use JIRA Sync option from requirement release tree menu." 

Sounds like this will require a lot of manual review to keep the content of the folders accurate. Also looks like I need to manually kick off a sync to pull in any changes made in Jira. I think it's pulling in changes to the tickets and also importing "new" tickets but I'm not sure. So I tried to use the "Jira Sync Config" option, but this always results in the imported structure being place in the "Release" folder which I am not able to move to "Project Requirements". 

The training video I found on "Jira Sync Config" does show the structure being created in the Release, so maybe that's the only way it's supposed to work, but it doesn't serve my needs. I could create a JQL and Jira Sync in each release, but I'm afraid I'll end up with multiple ZE items for any Jira items that is "re-imported" when we change the Fix Version in Jira (again, I only want 1 ZE item per Jira ticket). And the synced import will only bring in "new" content and will not remove content when  Jira ticket is moved to a new Fix Version.

Any help or guidance would be greatly appreciated. 

 

No RepliesBe the first to reply