Help Center
Help Center
  • Getting Started
    • What is Haystack?
    • Quick Start
      • Account Setup
      • Roles
        • For Executives
        • For Managers
        • For Product
  • Setup
    • Integrations
      • Jira
      • GitHub Cloud
      • GitHub Enterprise
      • GitLab
      • Bitbucket
      • Slack
    • Organization
      • Investments
      • Deployments
      • Invite users
      • Exclusions
    • Teams
      • Map members
      • Sprint success metric
      • Capacity
      • Alerts
      • SLAs
      • Risks
  • Features
    • Issues
    • Pull Requests
    • Epics
    • Retrospective
    • Release Notes
    • Investments
    • Alerts
    • Customizable Widgets
    • Flexible Reports
    • Team Metrics
    • List of All Metrics
    • API
    • Embedded reports
  • Admin
    • Security & Privacy
    • Data Sync
      • How to setup faster data sync for JIRA?
  • FAQ
    • Can I track Dora metrics?
    • What is Status Category?
  • Guides
    • First Principles of Engineering Metrics
    • Engineering Metrics (Video Series)
    • How to Improve Quality?
    • Sprint Planning
    • Daily Standups
    • Retrospectives
    • Identify Bottlenecks
  • Other
    • Changelog
Powered by GitBook
On this page

Was this helpful?

  1. Setup
  2. Teams

SLAs

Last updated 1 year ago

Was this helpful?

Track SLAs from our dashboard and get alerted on Slack when they are broken by setting SLAs on Haystack. Follow the below steps to set them up!

1. Head to

2. Head to SLAs

a. Set the numbers of days for the SLAs

Haystack automatically applies SLAs to any JIRA issue of type Bug. You can set a custom at-risk and broken day threshold based on the bugs priority

b. (Optional) Turn on SLA alerts

You may now head to Alerts on the same team settings to turn on Slack alerts when an SLA is at-risk or is broken

3. Track SLAs on Active Cycle page

Once SLAs are set, you can now filter your JIRA issues based on SLAs from your Haystack dashboard

team settings