# Alerts

We'll go over each alert Haystack has.&#x20;

<figure><img src="/files/11RUUUsBhlmGjaSJDTDf" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Check how to setup [Alerts](/setup/teams/alerts.md)
{% endhint %}

## Risks

### Issue Stuck

**Triggers:** When an issue passes it's [stuck configs](/setup/teams/risks.md).

<figure><img src="/files/uG5bilgNmhjJTOeiB7qZ" alt=""><figcaption></figcaption></figure>

### Bug SLA Risk

**Triggers:** When a bug passes it's [at risk configs](/setup/teams/slas.md).

<figure><img src="/files/uJxZsg7k2aS0wwL3uIeP" alt=""><figcaption></figcaption></figure>

### Bug SLA Broken

**Triggers:** When a bug passes it's [broken configs](/setup/teams/slas.md).

<figure><img src="/files/KsE1yp4GuY6kbLzhvJlz" alt=""><figcaption></figcaption></figure>

### PR Not Linked

**Triggers:** When PR doesn't have a [link to an issue](/features/issues.md#h_99088c5f36). Haystack has a 10 minute delay before sending the alert.

<figure><img src="/files/dsR2frlzHGCd0oXOlRgv" alt=""><figcaption></figcaption></figure>

### Sprint Overcapacity

**Triggers:** When issue count or storypoint count passes [capactiy limit](/setup/teams/capacity.md). Haystack has a 30 minute delay before sending the alert.

<figure><img src="/files/r9oti1mD8X8PnYTOD552" alt=""><figcaption></figcaption></figure>

## Progress & Achievements

### Mid-sprint Review

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

<figure><img src="/files/SgfNN8jeY2AOu3iQKjKY" alt=""><figcaption></figcaption></figure>

### Cycle Completed

For Sprint & Kanban teams we have 2 different alerts

**Triggers:**&#x20;

* For Kanban, Monday 9AM (organizations default timezone)
* For Sprint, when sprint is tagged as completed

<figure><img src="/files/B5j13EGcAi2O8NqpjKk4" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/CKtzQccYVnvOVIw9FVKZ" alt=""><figcaption></figcaption></figure>

### Release Notes

For Sprint & Kanban teams we have 2 different alerts

**Triggers:**&#x20;

* For Kanban, Monday 9AM (organizations default timezone)
* For Sprint, when sprint is tagged as completed

<figure><img src="/files/7HSFR1WX6Wl7OjhgnY6o" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/E6CBxfXfZohz034k4NWZ" alt=""><figcaption></figcaption></figure>

### Epic Completion

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

<figure><img src="/files/zt94hF9aEmK1g3ceLOi7" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.usehaystack.io/features/alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
