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
  • Risks
  • Issue Stuck
  • Bug SLA Risk
  • Bug SLA Broken
  • PR Not Linked
  • Sprint Overcapacity
  • Progress & Achievements
  • Mid-sprint Review
  • Cycle Completed
  • Release Notes
  • Epic Completion

Was this helpful?

  1. Features

Alerts

Last updated 11 months ago

Was this helpful?

We'll go over each alert Haystack has.

Check how to setup Alerts

Risks

Issue Stuck

Triggers: When an issue passes it's stuck configs.

Bug SLA Risk

Triggers: When a bug passes it's at risk configs.

Bug SLA Broken

Triggers: When a bug passes it's broken configs.

PR Not Linked

Triggers: When PR doesn't have a link to an issue. Haystack has a 10 minute delay before sending the alert.

Sprint Overcapacity

Triggers: When issue count or storypoint count passes capactiy limit. Haystack has a 30 minute delay before sending the alert.

Progress & Achievements

Mid-sprint Review

Triggers: When ~50% of time passed between sprint start date & sprint end date.

Cycle Completed

For Sprint & Kanban teams we have 2 different alerts

Triggers:

  • For Kanban, Monday 9AM (organizations default timezone)

  • For Sprint, when sprint is tagged as completed

Release Notes

For Sprint & Kanban teams we have 2 different alerts

Triggers:

  • For Kanban, Monday 9AM (organizations default timezone)

  • For Sprint, when sprint is tagged as completed

Epic Completion

Triggers: All issues under an epic is moved to Done status category