> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/data-quality-v2/cases.md).

# Cases

How incidents are grouped into cases, and how your team works through them

When a monitor run fails, Decube raises an **incident** and files it under a **case**.

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fi1O0Wfev4pNWMZk1dyMq%2FSCR-20260925-jlsm.png?alt=media&amp;token=7f639808-863d-4269-84cc-1e9e9ab14505" alt=""><figcaption></figcaption></figure>

The case is the unit your team works: it collects every incident from the same monitor for the same run of a problem, so a table that fails eight nights running gives you one case with eight incidents rather than eight separate things to triage.

{% embed url="<https://youtu.be/Xz2QggEXf-8>" %}

### The lifecycle

A case opens with its first incident and stays **Open** while further incidents land in it. You close it once the underlying problem is fixed. If the monitor fails again afterwards, Decube opens a fresh case, which gives you a clean record of how many separate times the problem occurred.

You can also **mute** a case, which stops it generating alerts while you keep working on it.

### The metrics row

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2FcAXPNokhfw0Yrh1JcFyl%2FSCR-20260925-jmcj.png?alt=media&amp;token=fc223559-6404-4c05-999b-96bab7230354" alt=""><figcaption></figcaption></figure>

Four figures sit above the listing and cover every monitor type, independent of the filters you apply:

* **Open cases**, everything still to resolve.
* **Unassigned**, open cases with nobody named on them.
* **Average time to close**, over the last 30 days and the last 365 days.
* **New cases**, opened in the last 7 days against the 7 days before.

### The listing

Each row shows the monitor type, the monitor and its asset, the number of incidents in the case with the latest incident timestamp, the case status, the monitor's attributes, and the assignee. Rows sort by latest incident, most recent first. Search matches the monitor name.

<figure><img src="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2FW9l9fdZbj5nvvMxadnuZ%2FSCR-20260925-jmst.png?alt=media&amp;token=931ae760-b839-4537-9272-005b418b9542" alt=""><figcaption></figcaption></figure>

Filter by case status, data source, schema, assignee, custom attributes, monitor category and type, and by incident date range.

{% hint style="info" %}
The date range filter selects cases with at least one incident inside the window, so a long-running case opened months ago still appears. The incident count on the row stays the case lifetime total.
{% endhint %}

Filters persist while you move between the listing and a case, reset when you navigate away through the main menu, and are written into the URL so you can share a view to your colleague
