> For the complete documentation index, see [llms.txt](https://help.usehaystack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usehaystack.io/setup/teams/slas.md).

# SLAs

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** [**team settings**](https://dash.usehaystack.io/hub/settings)

<figure><img src="https://downloads.intercomcdn.com/i/o/923733406/7606e9e56387390e2fa24afc/Screenshot+2024-01-03+at+6.22.33%E2%80%AFPM.png" alt=""><figcaption></figcaption></figure>

**2. Head to SLAs**

<figure><img src="https://downloads.intercomcdn.com/i/o/923733801/1676bf9401fc1fb7c1654543/Screenshot+2024-01-03+at+6.47.23%E2%80%AFPM.png" alt=""><figcaption></figcaption></figure>

#### **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

<figure><img src="https://downloads.intercomcdn.com/i/o/923736515/21ed0954529cb7a608b4128e/Screenshot+2024-01-03+at+6.40.04%E2%80%AFPM.png" alt=""><figcaption></figcaption></figure>

**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

<figure><img src="https://downloads.intercomcdn.com/i/o/924687028/902d1b7d69f99812ea59cd7b/Screenshot+2024-01-04+at+5.52.55%E2%80%AFPM.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.usehaystack.io/setup/teams/slas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.