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 Jira integration for your Sleuth organization
  • Configuring Jira as a Metric Impact Source
  • Removing the integration

Was this helpful?

  1. Integrations
  2. Impact integrations
  3. Metric trackers

Jira metrics (Cloud / Data Center)

PreviousDatadogNextNewRelic

Last updated 1 year ago

Was this helpful?

About the integration

Jira is an issue tracking tool that integrates with Sleuth in support of various use cases (as a general , as an , etc.). This article is specific to using Jira as a metric impact source, which allows you to define a JQL query that returns a count of matching Jira issues and compare those against user-defined environment health thresholds. A common example here would be retuning the number of currently open bug tickets in Jira as an indicator of health.

Setting up the Jira integration for your Sleuth organization

If you've already set up the Jira integration for your Sleuth organization in support of any of the aforementioned use cases, you can skip ahead to below.

Otherwise, follow instructions for or to establish the integration, and then proceed to the next section to configure the impact source.

Configuring Jira as a Metric Impact Source

Once the Jira integration has been enabled for your Sleuth organization, perform the following steps to configure it as a Metric impact source.

  • Navigate to the Sleuth Project for which you'd like to add Jira as a metric impact source.

  • From the Project's left-hand menu, click Impact sources and select + Add impact source

  • In the field titled How do you track change failure?, select Metrics

  • If the Jira integration has been properly enabled for your Sleuth organization, the integration tile will show "enabled".

  • Click the tile to configure the Jira metric impact source.

  • In the following screen, give your metric impact source a name, specify which environment it's for, and enter a JQL query that returns a count.

  • Optionally, under Advanced settings, you can specify a threshold under which the count returned by the metric impact source will be considered healthy.

  • Test the connection to verify it's retuning the expected counts, and click Save.

  • That's it! Sleuth will now start verifying your deploys' health by tracking the values from your Jira metric. To view the new metric, simply choose your new impact source from the Project's left-hand navigation.

Removing the integration

To remove the Jira metric impact source from your Sleuth Project:

  1. Open the metric impact source from the Project's left-hand navigation menu.

  2. Click the cog in the upper-left-hand side of the screen and click Delete

deployment tracking issue integration
incident impact source
Configuring Jira as a Metric Impact Source
Jira Cloud
Jira Datacenter