> 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/risks.md).

# Risks

## Overview

Identify your blockers faster & get alerted by setting up risks on Haystack. 

## Configure

To configure risks in team settings, go to **team settings -> issue risks** or **team settings -> PR risks.**

## Basics

### **Issue risks**

Haystack provides two types of Issue risks:

1. **Stuck**\
   When issue takes too much time in status, Issue is considered as "stuck" when it stays too much time in particular status category or status. You can set your own rules when issue should be considered as "Stuck".
2. **Blocked**\
   Issue is considered as "Blocked" when it is marked in Jira as blocked by another issue. In order to mark issue as blocked in Jira, you need to [link issue](https://support.atlassian.com/jira-software-cloud/docs/link-issues/) and select "is blocked by" link type.

### **PR risks**

In PR risks, you will find potential risks you can configure for your pull requests. You may turn these on/off and set your threshold heres

<figure><img src="https://downloads.intercomcdn.com/i/o/923718354/983f6369c11b0da8b0a8f072/Screenshot+2024-01-03+at+6.30.31%E2%80%AFPM.png" alt=""><figcaption><p>PR risks settings page</p></figcaption></figure>

### **Quick filters**

Once Risks are set, you will see risky work on the **Issues** and **Pull Requests** pages in the right sidebar.

<figure><img src="https://downloads.intercomcdn.com/i/o/924689376/e12dd2cfd1651890f9197038/Screenshot+2024-01-04+at+5.52.55%E2%80%AFPM.png" alt=""><figcaption><p>Issue page risks filters</p></figcaption></figure>

### **Alerts**

Setup [Slack alerts](/setup/teams/alerts.md) and Haystack will notify you when risk is detected.

<figure><img src="https://933147321-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbiIqB8vq91hNrILQ1MAF%2Fuploads%2Fa87wYNcnVBGdJlujeAVh%2Fimage.png?alt=media&amp;token=0fb01fd0-fe7d-4459-b5ea-d3c14e4da354" alt=""><figcaption><p>Example of not linked Pull Request risk alert</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.