# Risks

## Overview

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

## 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](https://help.usehaystack.io/setup/teams/alerts) 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&#x26;token=0fb01fd0-fe7d-4459-b5ea-d3c14e4da354" alt=""><figcaption><p>Example of not linked Pull Request risk alert</p></figcaption></figure>
