Integrations

Jira Marketplace App

Install the Koalr app from the Atlassian Marketplace to see deploy risk scores directly on Jira issues.

The Koalr Jira Marketplace app surfaces deploy risk data inside Jira — no context switching required. See the risk score and deployment prediction for every linked PR directly on the issue panel, and monitor your team's DORA metrics from a Jira dashboard gadget.

What it includes

Deploy Risk panel (on every issue)

When a Jira issue has linked pull requests, the Deploy Risk tab shows:

  • Risk score (0–100) and level badge (LOW / MEDIUM / HIGH / CRITICAL) for each PR
  • DDL migration warning when detected
  • Change size: additions, deletions, files changed
  • Direct link to the full signal breakdown in Koalr

PRs are linked automatically when they reference the issue key in their title or branch name (e.g. fix/PROJ-123-payment-bug).

Deployment prediction panel

Below the risk score, the panel shows a forward-looking deployment prediction for each PR:

  • Recommendation banner — color-coded action (e.g. "High risk — recommend additional review before merging") based on the predicted outcome
  • Failure probability — estimated likelihood this deployment causes a production incident
  • MTTR estimate — predicted mean time to restore if this deployment does fail
  • Blast radius — affected service tier (LOW / MEDIUM / HIGH / CRITICAL) and estimated number of downstream services impacted
  • Incident severity — predicted severity level if a failure occurs

This gives engineers the full deployment risk picture without leaving the Jira issue.

Risk glance badge

A small colored badge in the issue sidebar shows the highest risk score across all linked PRs at a glance — without opening the full panel.

DORA dashboard gadget

Add the Koalr gadget to any Jira dashboard to see your team's four DORA metrics — deploy frequency, lead time, change failure rate, and MTTR — alongside your DORA tier (Elite / High / Medium / Low).

Installation

From the Atlassian Marketplace

  1. Go to your Jira site → Apps → Explore more apps
  2. Search for Koalr
  3. Click Get appGet it now
  4. You'll be prompted to grant the required permissions (read Jira issues, Forge Storage for your API key)

Connect your Koalr account

After installation:

  1. Go to Apps → Manage your apps → Koalr → Settings
  2. In the Koalr Settings page, enter your Koalr API key
  3. Click Save

To get an API key:

  1. Log in to app.koalr.com
  2. Go to Settings → API Keys
  3. Click Create API Key
  4. Select at minimum the read:prs scope (add read:dora if you want the dashboard gadget)
  5. Copy the key — it's shown once

Permissions

The app requests:

PermissionWhy
read:jira-workRead the current issue key to look up linked PRs
storage:appStore your Koalr API key securely per Jira site
External fetch to api.koalr.comFetch risk scores and DORA metrics from Koalr

The API key is stored in Atlassian Forge Storage, encrypted at rest, and scoped to your Jira site. It is never shared with other organizations.

How PR linking works

Koalr links pull requests to Jira issues by scanning PR titles and branch names for issue key patterns (e.g. PROJ-123). This happens automatically as PRs are opened or synchronized via the GitHub App.

For the link to appear in the Jira panel:

  • Your GitHub account must be connected to Koalr
  • The PR title or branch name must include the Jira issue key
  • The Jira integration must be active (see the Jira integration guide)

Adding the DORA gadget to a dashboard

  1. Open a Jira dashboard → Edit
  2. Click Add gadget
  3. Search for Koalr
  4. Select Koalr — Engineering Metrics and click Add gadget
  5. Configure the time period (7 / 30 / 90 days) and save

Troubleshooting

Panel shows "No linked pull requests"

  • Confirm the PR title or branch references the issue key (e.g. PROJ-123)
  • Check that your GitHub integration is active in Koalr
  • Allow up to 5 minutes for newly opened PRs to sync

"Connect Koalr" prompt appears after saving the API key

  • Verify the key starts with koalr_
  • Confirm the key has the read:prs scope
  • Try removing and re-adding the key in App Settings

Risk score shows "Not scored"

  • Deploy risk scoring runs within ~60 seconds of a PR being opened
  • Older PRs (before Koalr was connected) may not have scores — open a new PR to trigger scoring

Prediction panel shows "—" for failure % or MTTR

  • Deployment prediction requires at least 10 historical deployments in Koalr to calibrate the model
  • Connect a deployment platform (GitHub Actions, Vercel, Argo CD, etc.) to start recording deploy outcomes
  • Predictions become available once Koalr has enough outcome data for your organization

Blast radius shows "Unknown"

  • Blast radius analysis requires the service dependency graph to be populated
  • Connect Datadog, Argo CD, or enable the GitHub Actions integration to build the dependency map