Jira Integration

The Jira integration pulls sprint data, issue cycle time, and project health into Koalr. Combined with GitHub data, Jira cycle time feeds directly into your DORA lead time calculations.

Supported versions

Koalr supports Jira Cloud only. Jira Server and Jira Data Center are not currently supported. If your organization runs Jira Server or Data Center, contact support — we track demand for on-premise Jira support.

Connecting Jira Cloud

Prerequisites

• You must be a Jira project admin or organization admin in Jira Cloud to complete the OAuth connection.
• Your Jira Cloud site URL (e.g., yourcompany.atlassian.net) should be ready.

OAuth connection steps

1. Go to Settings → Integrations in Koalr.
2. Click Connect Jira.
3. You are redirected to Atlassian's OAuth 2.0 authorization page.
4. Select the Atlassian site you want to connect (if you have multiple sites, pick the one that contains your engineering projects).
5. Click Accept to authorize Koalr.
6. You are redirected back to Koalr's integrations page.

OAuth scopes requested

Koalr requests the read:jira-work scope, which grants read-only access to:

• Issues and issue fields (summary, status, assignee, timestamps)
• Sprints and active/completed sprint data
• Projects and project configurations
• Epic and story hierarchies

Koalr never writes to Jira — we do not create issues, update fields, or transition issue statuses.

What Koalr syncs from Jira

Issues

Koalr imports all issues from projects associated with your connected teams. For each issue, we track:

• Status transitions — timestamps for each status change, used to compute cycle time
• Assignee — mapped to Koalr users by email address
• Issue type — Story, Bug, Task, Epic (used for filtering in dashboards)
• Resolution date — used as the completion timestamp for DORA lead time calculations

Sprints

Sprint data is synced from Jira Scrum boards. Koalr reads:

• Sprint name, start date, and end date
• Issues included in each sprint and their completion status
• Velocity (story points completed per sprint, when story points are used)

Sprint data appears in the Team Velocity dashboard and Onboarding Velocity views.

Projects

Koalr imports all active projects visible to the connected Jira account. Projects can be associated with Koalr teams in Settings → Teams.

Cycle time

Cycle time is calculated from Jira status transition timestamps. Koalr uses the first transition into an "In Progress" state as the start time and the first transition into a "Done" state as the end time. Custom statuses are mapped using your Jira workflow configuration.

Cycle time from Jira is combined with PR review time from GitHub to produce the full lead time metric shown in your DORA dashboard.

Real-time updates via webhook

After the initial sync, Koalr registers a Jira webhook to receive real-time issue update events. This means issue status changes appear in Koalr within seconds rather than waiting for a periodic sync.

The webhook is registered automatically during the OAuth connection. You can verify its status in Settings → Integrations → Jira → View webhook.

Initial sync time

The initial Jira sync imports 90 days of issue history. For organizations with:

• < 1,000 issues: sync completes in under 5 minutes
• 1,000–10,000 issues: 10–30 minutes
• > 10,000 issues: up to 2 hours

Sync progress is visible in Settings → Integrations → Jira.

Disconnecting Jira

To disconnect Jira, go to Settings → Integrations → Jira and click Disconnect. Historical Jira data already synced to Koalr is retained for 30 days after disconnection, then permanently deleted.