Jira Service Management (alerts)
Leak events are posted to Jira Service Management’s Operations section as alerts.
How it works
The connection uses the tenant identifier and an API token. Alerts are routed according to your on-call schedule.
Every alert carries a deduplication key specific to the event; if the same event is processed again, no new alert is opened.
The Operations feature is not in the free plan; Standard or above is required.
Severity mapping
| Dark Radar | Jira Service Management |
|---|---|
| Critical | P1 |
| High | P2 |
| Medium | P3 |
| Low | P4 |
| Info | P5 |
Limits
Only alerts are created. The on-call schedule, users and tickets are not changed.
Only leak alerts go out; a scan summary does not wake the rotation.
The leaked value itself is not in the alert.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.