Integrations

Jira

ARI can automatically create Jira issues for confirmed bugs found during an analysis. Each issue includes the bug description, severity, affected URL, and a link back to the full ARI report.

SETUP

1. 1Go to Dashboard → Integrations → Jira.
2. 2Enter your Jira domain (e.g. mycompany.atlassian.net), project key, and an API token from your Atlassian account settings.
3. 3Click Connect. ARI will verify access to the project.
4. 4Per project, choose whether to create Jira issues automatically on every analysis or only when the verdict is WARNING or NOT SAFE.

EXAMPLE JIRA ISSUE BODY

Summary: [ARI] Checkout flow fails on mobile Safari (risk: HIGH)

*Source:* ARI Release Check — v2.4.1-rc1
*Project:* my-saas-app
*Verdict:* WARNING | Risk Score: 62
*Severity:* High
*Affected URL:* https://staging.myapp.com/checkout

*Description:*
The payment confirmation step does not complete on mobile Safari 17.
Users see a blank screen after clicking "Pay Now". Affects ~18% of checkout sessions.

*Evidence:*
- HTTP 500 observed on POST /api/checkout in 3 of 5 simulated flows
- Console error: TypeError: Cannot read properties of undefined (reading 'stripe')

*Report:* https://app.ari.sh/dashboard/reports/anlys_01jaz87kp9m3t

Linear

The Linear integration creates issues in your chosen team and project, with priority and label mapping based on ARI severity levels.

SEVERITY TO PRIORITY MAPPING

Connect at Dashboard → Integrations → Linear. You will need a Linear personal API key or OAuth connection. Choose the target team and project during setup.

Datadog

ARI can send analysis events to Datadog so you can correlate release risk data with your observability metrics. Events appear in the Datadog Event Stream with tags for verdict, risk score, and project.

SETUP

1. 1Go to Dashboard → Integrations → Datadog.
2. 2Paste a Datadog API key with Events Write permission.
3. 3Optionally add custom tags to apply to all ARI events (e.g. env:staging, team:platform).

EXAMPLE DATADOG EVENT

{
  "title": "ARI analysis complete — WARNING (score: 62)",
  "text": "Project: my-saas-app | Label: v2.4.1-rc1 | Bugs: 3",
  "priority": "normal",
  "alert_type": "warning",
  "tags": [
    "ari:verdict:WARNING",
    "ari:project:proj_01j9xkz2p4m8v",
    "ari:risk_score:62",
    "env:staging"
  ],
  "source_type_name": "ARI"
}

PagerDuty

For teams that treat a NOT SAFE verdict as an incident, ARI can trigger a PagerDuty alert immediately upon completion. This lets on-call engineers review the report before a bad release reaches production.

SETUP

1. 1Create a new Service in PagerDuty with Events API v2 integration.
2. 2Copy the Integration Key from the service's Integrations tab.
3. 3Go to Dashboard → Integrations → PagerDuty and paste the key.
4. 4Choose which verdicts trigger an alert: NOT SAFE only (recommended) or WARNING and above.

// PagerDuty event payload sent by ARI
{
  "routing_key": "<your-integration-key>",
  "event_action": "trigger",
  "payload": {
    "summary": "ARI: NOT SAFE verdict — my-saas-app (v2.4.1-rc1)",
    "severity": "critical",
    "source": "ARI Release Intelligence",
    "custom_details": {
      "project": "my-saas-app",
      "label": "v2.4.1-rc1",
      "verdict": "NOT SAFE",
      "risk_score": 91,
      "confirmed_bugs": 7,
      "report_url": "https://app.ari.sh/dashboard/reports/anlys_01jaz87kp9m3t"
    }
  }
}