Date: Thu, 28 Mar 2024 15:43:51 +0000 (UTC) Message-ID: <301685492.21.1711640631002@9bbafe705431> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_20_2113256492.1711640631002" ------=_Part_20_2113256492.1711640631002 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Improvements
A Zephyr administrator can now choose whether to create Jira defects via= Zephyr=E2=80=99s File New Defect dialog or directly in Ji= ra. This is done by using the new Create defects in Jira t= oggle switch on the Administration > Jira Integration p= age:
When the toggle is ON, Jira=E2=80=99s Create issue dialog =
opens in a new tab when you start filing a defect in Zephyr and you can cre=
ate an issue directly in Jira. If the toggle is OFF, defects are created in=
Zephyr.
Note: We recommend toggling on this option if =
your Jira issues have required custom fields.
Parser templates have a new =E2=80=9Cstrict=E2=80=9D option that = controls whether $-expressions such as ${A.B.C} search for XML no= des recursively.
Improved the error message about incorrect JQL queries.
Various performance improvements.
Single sign-on
Users could still use their internal credentials to log in to Zephyr whe= n secondary authentication was disabled. (ZEPHYR-31910)
Jira integration
An error occurred upon clicking the Defects Linked to Execution link on = the Release Summary page. (ZEPHYR-31820)
Parsing
Sometimes, duplicate test cases were created after importing an XML file= . (ZEPHYR-31748)
To learn how to upgrade to version 7.4, see Upgrading Zephyr Enterprise.