Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • About the integration
  • Setting up the integration
  • Configuring the integration
  • To set the default issue tracker
  • To change the default issue tracker
  • Removing the integration

Was this helpful?

  1. Integrations
  2. Issue tracker integrations

Linear

PreviousJira Data CenterNextShortcut

Last updated 3 years ago

Was this helpful?

About the integration

This integration enables Sleuth to use Linear as a deployment issue tracker. When you deploy, Sleuth will automatically connect your Linear issues to the deploys, so you can always find the source of your changes later.

Integration with Linear is made at the Sleuth organization level. More than one can be integrated with an organization. Although you can have multiple projects within an organization, each project can only be configured to use a single issue tracker.

Once Linear is configured as an issue tracker, every time the Linear issue key is included in a deploy's commit message, Sleuth will automatically link that deploy with the corresponding issue in Linear.

Setting up the integration

To set up the Sleuth Linear integration

  1. Click Integrations in the left sidebar, then click Issue Trackers.

  2. In the Linear tile, click connect.

  3. Enter the Personal API Key of your Linear instance into the corresponding field, then press Save. To quickly access your Linear instance to obtain an API key, click generate. You will be taken to the Personal API keys section in your Linear dashboard. =

  4. The message Linear enabled is displayed in the tile. Note the Set default issue tracker dropdown; you will be setting the default issue tracker in the next section.

Configuring the integration

After setting up the Linear integration, you must designate which Sleuth project to use as the default issue tracker. If you are configuring the integration immediately after setting it up, you can go directly to step #2 in To set the default issue tracker below.

To set the default issue tracker

  1. Click on Integrations in the left sidebar, then on Issue Trackers.

  2. Click on the Linear Set default issue tracker dropdown (see screenshot above).

  3. All projects in the organization are displayed. Select which project you'd like to set Linear as the default issue tracker for.

To change the default issue tracker

  1. Click on Project Settings in the left sidebar, then select Details.

  2. Select an issue tracker. The integration must be connected via the organization before it's displayed here.

  3. Press Save.

Removing the integration

If you wish to dissolve the Linear integration for the organization

  1. Click on Integrations in the left sidebar, then on Issue Trackers.

  2. In the Linear integration card, click disconnect.

The Linear integration is disconnected and no longer available to any projects within that organization. Any projects that used the Linear integration will need a new default issue tracker selected.

To set a new default issue tracker

  1. Click on Project Settings in the left sidebar, then select Details.

  2. Select a new default issue tracker. The integration must be connected via the organization before it's displayed here.

  3. Press Save.

The Linear integration is disconnected and no longer available to any projects within that organization. You will need to select a new default issue tracker for any projects that used the Linear integration. Simply follow the instructions in the section above: To set a new default issue tracker.

issue tracker