Ability to map one Zephyr project to multiple Jira projects
As a manager working on a project that uses multiple Jira projects for different teams, I'd like to be able to manage all these Jira projects from a single Zephyr project. As part of this, I'd expect to be able to import requirements from these Jira projects, as well as file defects into any of these Jira projects. OLD ID :- ZENT-I-17Jira - ZephyrEnterprise app, need some configuration options
To get any Zephyr information to show up in Jira, I need to (for every single ticket/issue) click on the elipsis menu to enable the traceability report widget, and then click Load Report. The Load Report is cumbersome enough, but i'm finding this integration unusable when you combine that with hiding the integration altogether in the issues. Please consider adding the ability to auto-display Zephyr stats on a per-project basis. OR just load it for anything with matching testcases, and autoload the traceability report (or have autoload be a setting). Some kind of change is necessary regardless, because the integration as it stands now definitely falls short of what we need.Ability to link a Defect to a Requirement in Jira automatically
As Zephyr User When linking a Defect to a Test (Execution) While the Test being linked has been mapped to Jira requirement(s) in Zephyr I want the same Defect to get linked to this Requirement(s) in Jira automatically using Jira link type 'blocks' Link type can be configurable in Custom Configurations. OLD ID:- ZENT-I-369
Ability to export Zephyr Enterprise Test Case ID from Jira Cloud when both are integrated
Links to case ID: #00544511 When raising a defect in Zephyr Enterprise 7.15.1, the Jira "Create New Issue" screen is launched and the user can raise the defect in Jira as usual and then link the Jira Issue ID back to the Zephyr test case. Once the user has established this link and on opening the Jira issue, I can see the integration passes the Zephyr Test Case ID through. I'd like to be able to Export this as a data element out of Jira, but it seems not to persist in the Jira database (as is not a default or Custom field).