> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt > Use this file to discover all available pages before exploring further. # Managing Incidents > Explore incident workflows that document, notify, and assign resolution steps for quality issues across assets. # Managing Incidents Use this guide to manage incidents from the dashboard through to resolution. ## Incident Dashboard The Incident Dashboard gives a real-time overview of incident health and lists all active and resolved incidents in one place. Incident Manager Dashboard ### Summary Metrics Four cards at the top of the dashboard show key incident statistics at a glance: * **Open Incidents**: Total number of currently active incidents. * **Resolved Incidents**: Total number of closed incidents. * **Response Time**: Average time from incident creation to first acknowledgement. * **Resolution Time**: Average time from incident creation to resolution. ### Filters Use the filter bar to narrow the incident list: * **Test Case**: Filter by a specific test case name. * **Assignee**: Filter by the team member assigned to the incident. * **Status**: Filter by current status (New, ACK, Assigned, Resolved). * **Date Filter**: Choose the date field to filter by (for example, Created at). * **Date Range**: Set a custom date range. ### Incident List Each row in the table represents one incident and shows: * **Test Case Name**: The test case that triggered the incident. * **Table**: The data asset associated with the test case. * **Last Updated**: Date and time of the most recent activity. * **Status**: Current stage of the incident (New, ACK, Assigned, Resolved). * **Severity**: Severity level assigned to the incident. * **Assignee**: The team member responsible for resolution. ## Incident Status Change Update the incident status to reflect the current stage of the resolution process. The incident owner assigns it to a team member for resolution. ### Steps to Change Incident Status 1. Navigate to the Incident Dashboard. 2. In the **Status** column, click the status dropdown next to the incident whose status you want to change. 3. Select a status. Incident Status Change ## Incident Resolution Once you resolve an incident, close it officially. Add a Root Cause Analysis (RCA) to the resolution comments to provide context for what went wrong and how it was fixed. ### Steps to Resolve and Close an Incident 1. Verify that all necessary steps to resolve the incident have been completed. 2. Describe the RCA in the resolution comments. 3. Change the status of the incident to **Resolved**. 4. Confirm the closure to update the incident in the dashboard. Incident Resolution ## Incident Activities Each incident includes a detailed timeline where all activity is recorded. This timeline provides a comprehensive view of the incident's lifecycle, including key events, RCA documentation, and closure updates. ### How to View Incident Activities 1. Open the incident from the Incident Dashboard. 2. Navigate to the **Incident** tab. 3. Review the chronological events, RCA, and closure updates associated with the incident. Incident Activities ## Set Up Alerts for Incident Activity To receive notifications when an incident is created, updated, commented on, or assigned, configure an alert with **Source = Task**. Incidents in Collate are Task threads with task type `RequestTestCaseFailureResolution`. Alert sources are matched by thread type, not task type — so if you configure an alert with Source = **Conversation**, it will never fire for incidents. ### Steps to Create an Incident Alert 1. Click the **Profile** icon and navigate to **Settings** > **Notifications** > **Alerts**. 2. Click **Add Alert**. 3. On the **Add Alert** page, do the following: 1. Add a unique **Name** and **Description** (optional). 2. Set **Source** to **Task**. 3. (Optional) Add a **Mentioned User** or **Team** filter to limit alerts to incidents where a specific person or team is @-mentioned. 4. Set **Destination** to Slack, MS Teams, email, or internal Collate users. 4. Click **Save** to create an alert. **Note**: The Task source covers all structured workflow tasks — incidents, description requests, tag requests, and approval workflows. There is currently no filter to restrict to incidents only. If you only want incident notifications, configure a dedicated alert and instruct your team to use that alert's destination channel for incident discussions. For a full reference of alert source entities and their available filters, see [System & Governance Notifications](/ai-2-0/how-to-guides/data-quality-observability/alerts-notifications/system-governance-notifications).