Skip to main content

Phase 1 - Connect Your Systems

In this phase, you will connect your source control provider and project management tool to LinearB. Once connected, LinearB begins ingesting commits, pull requests, and issue data across your engine…

Steven Silverstone
Updated by Steven Silverstone

In this phase, you will connect your source control provider and project management tool to LinearB. Once connected, LinearB begins ingesting commits, pull requests, and issue data across your engineering organization.

Goal of this phase: LinearB successfully receives engineering activity data.

Estimated time: 10–25 minutes

Before You Begin

Make sure you have the required access before starting the integration process.

  • LinearB: Company Admin role
  • Git provider: Admin or organization-level access
  • Project management tool: Admin access
Enterprise best practice
Use a dedicated service account to connect integrations. This prevents integrations from breaking if an employee leaves or loses permissions.

Step 1 — Connect Your Git Provider

LinearB analyzes commits, pull requests, merges, and repository activity from your Git provider. This integration is required for all engineering analytics and delivery metrics.

Supported Git Providers

  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps

Follow the appropriate guide to connect your Git provider:

Step 2 — Connect Your Project Management Tool

LinearB links pull requests to work items from your project management system. This connection enables metrics such as Cycle Time, Coding Time, and Pickup Time.

Supported Project Management Tools

  • Jira
  • Azure Boards
  • Shortcut

Follow the appropriate integration guide:

Initial Data Sync

After integrations are connected, LinearB begins synchronizing data.

  • Recent activity appears within 30–60 minutes
  • Historical data backfill may take 2–3 hours

You can continue the setup process while the historical backfill completes.

Verify Phase 1 — Confirm Data Is Flowing

Before moving to Phase 2, confirm that integrations are working correctly.

Verify Git Integration

  1. Navigate to Settings → Integrations → Git
  2. Confirm status shows Connected
  3. Verify repositories appear in the list
  4. Confirm recent commit timestamps are updating

Verify Project Management Integration

  1. Navigate to Settings → Integrations → Project Management
  2. Confirm status shows Connected
  3. Verify boards/projects are visible

What Success Looks Like

  • Repositories appear in LinearB
  • Pull requests begin appearing in dashboards
  • Projects/boards are selectable during configuration

Common Integration Pitfalls

Most integration issues are caused by permission or configuration problems. Check the following if data does not appear.

Git Integration Issues

  • Organization access was not granted during OAuth authorization
  • Repositories were not selected during setup
  • Integration account lacks repository read permissions
  • Enterprise Git policies blocked OAuth access

Project Management Integration Issues

  • Jira project permissions prevent issue visibility
  • Azure Boards organization access not granted
  • API token expired or revoked

Sync Delays

  • Large repositories may require additional time for historical backfill
  • Initial sync may take several hours for enterprise-scale environments
If integrations still fail:
  • Disconnect and reconnect the integration
  • Verify admin permissions for the integration account
  • Check repository and project visibility settings
  • Contact LinearB Support if the issue persists

Next Step

Once integrations are working and data is flowing, configure data accuracy settings in the next phase.

Continue to Phase 2 — Configure Data & Metrics →

How did we do?

Phase 2 — Configure Data & Metrics Accuracy

Contact