Using Jira Webhooks

Starting October 11, 2024 (Zephyr Enterprise 8.2), the Zephyr Enterprise documentation moved from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise documentation page. Please see: Using Jira Webhooks | Zephyr Enterprise Documentation

You can use Jira Webhooks to update the following:

  1. Jira Requirement Sync
    Jira Requirement Sync ensures that any changes made to issues in Jira are reflected accurately in Zephyr using Webhook. The following are the conditions when issues get added, updated, or deleted from Zephyr Requirement via webhook:

    • Whenever an issue is created in Jira and satisfies the JQL specified in Zephyr Requirement, the issue is automatically added to Zephyr using a webhook.

    •  Whenever an issue is updated in Jira and it satisfies the JQL specified in Zephyr Requirement, the corresponding issue in Zephyr is promptly updated using a webhook.

    • If you delete an issue in Jira that satisfies the JQL used in Zephyr Requirement, the issue gets deleted from Zephyr using a webhook.

  2. Jira Import:
    Jira Import facilitates efficient synchronization between Jira and Zephyr.
    Whenever you update an issue in Jira and if the issue is present in Zephyr Requirement, the corresponding issue in Zephyr gets updated using a webhook.
    When utilizing Jira Import functionality, you can update the following fields in an issue in Zephyr using webhook.

    • Status

    • Priority

    • Summary

  3. Defect (Linked to Execution)
    When an issue is linked to a Test Execution, any subsequent updates made to it automatically reflects in the Test Execution Defect Link.
    In Zephyr, using webhook you can update the following fields for the linked defects:

    • Status

    • Priority

    • Summary

In Zephyr, you can view the updates for the linked defects in:

  • Open and Overall Defect gadget

  • Release Summary page

  • Test Execution Defect link on hover

  • Defect Tracking Summary Page

In Defect Tracking Search window, we fetch the issue directly from Jira. There is no webhook associated with the defect tracking.

Â