Skip to content

Register the Jira Webhook

Without a webhook, changes made in Jira reach Qualytics shortly after the anomaly is opened and on a background sweep that runs hourly by default. Registering the integration's webhook in Jira makes Jira notify Qualytics the moment an issue changes, so linked ticket cards, statuses and comments refresh within seconds. The webhook is optional, and the view refresh and the sweep keep working either way. See When the read-back happens for how the three triggers relate.

Permissions

Reading the webhook URL in Qualytics requires the Manager or Admin role. Creating the webhook in Jira requires Jira administrator access, because webhooks live in Jira's own system settings.

Steps

Step 1: In the left side panel, click Settings .

Step 2: The Connections tab opens by default. Click the Integrations tab.

Step 3: Find the Jira row, which shows Connected, click the vertical ellipsis next to the status, and click Edit .

Step 4: In the Edit Jira Integration modal, find the Webhook URL box and click Copy .

Step 5: In Jira, create a webhook with that URL as its target. Webhooks are created by a Jira administrator from Jira's system settings, and the exact path depends on your Jira version.

Step 6: Subscribe the webhook to issue and comment events, so Qualytics is told when an issue changes and when a comment is written, edited, or deleted on it.

Step 7: Save the webhook in Jira. From then on, a change made to a linked issue is reflected on its anomaly within seconds.

Note

The Webhook URL box only exists for an integration that has been saved, because the URL is minted for that connection. When adding a new integration, create it first, then reopen it with Edit to copy the URL.

The URL is a credential

The URL embeds a secret, and that secret is the webhook's whole authentication, so share it only with people who could edit the integration anyway. The payload itself is never trusted. Qualytics only reads which issue changed and then re-reads that issue with its own stored credentials, so nothing sent to the webhook is written to the platform directly, and events for issues that are not linked to any anomaly are ignored.

Tip

Jira fires the webhook for every issue in its scope, not only the ones linked in Qualytics. Unlinked issues are dropped on arrival, so nothing breaks, but on a busy site you can cut the noise by scoping the webhook to the projects Qualytics uses, when your Jira offers a filter for it.