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 Jira Cloud integration for your Sleuth organization
  • Custom HTTP headers
  • Using the integration
  • To set Jira as the issue tracker on a Project:
  • Removing the integration

Was this helpful?

  1. Integrations
  2. Issue tracker integrations

Jira Cloud

PreviousIssue tracker integrationsNextJira Data Center

Last updated 1 year ago

Was this helpful?

About the integration

The Jira integration allows Sleuth to use Jira Cloud as a deployment issue tracker. When you deploy, Sleuth will automatically connect your Jira issues to the deploys, so you can always find the source of your changes later. Direct links to related Jira projects are provided in the deploy cards, allowing you to quickly see the Jira issues that affect your deploys.

Integration with Jira Cloud 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 configured to use a single issue tracker. Bitbucket, due to its own integration with Jira Cloud, can be used as one of those since Bitbucket can automatically connect to your Jira issues as long as both of those Atlassian products are both logged in with the same account. Bitbucket can also serve as a code deployment source change.

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

Check out the Sleuth for Jira integration .

Setting up Jira Cloud integration for your Sleuth organization

To set up the Sleuth Jira Cloud integration for your Sleuth organization:

  1. Click your avatar in the top-right of the navigation bar and click Integrations in the Organization section.

  2. In the Jira Cloud tile, click Enable.

  3. Enter the fully qualified URL of your Jira Cloud instance, the authorized User's Email, and the corresponding API Token into the respective fields, then click Save. To quickly access your Jira Cloud instance to obtain an API token, click the generate link in the title.

Custom HTTP headers

If you using Jira on-premise behind Cloudflare access or similar, Sleuth might need to include some HTTP headers in order to reach your instance. In order to set Sleuth to send any custom HTTP headers when making requests:

  1. In the Jira dialog, click on the Advanced setting

  2. Enter comma separated list of custom headers you want Sleuth to include

Using the integration

Setting up the Jira Cloud integration represents the groundwork for later issue tracking. To actually start tracking issues, you need to configure your Projects to use the integration for that purpose.

To set Jira as the issue tracker on a Project:

  1. Navigate to the Project you wish to use Jira as issue tracker with

  2. Click on Settings in the left sidebar, then select the Details tab.

  3. Click Save.

The Issue Integration Provider setting is defined on a Project-level basis, so it needs to be applied to each Project individually.

Removing the integration

If you wish to disconnect the Jira Cloud integration for the organization:

  1. Click your avatar in the top-right of the navigation bar and click Integrations in the Organization section.

  2. In the Jira Cloud tile, click the ∨ symbol to expand the tile.

  3. A list of all of your Jira connections should be displayed.

  4. Click Remove for each of the connections you wish to remove.

The integration is fully disconnected once all Jira Cloud connections are removed.

Select your Jira integration from the list in the Issue Integration Provider dropdown. Please note that the integration must first be set up at the organization level before it can be selected.

Once a connection is removed, it is no longer available for any projects within the organization. Any projects that used that particular Jira Cloud connection will need to have a .

new issue tracker connection or a completely different issue tracker selected
issue tracker
in the Atlassian Marketplace