> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/ticket-overview.md).

# Ticket Overview

The **Ticket overview** widget summarizes tickets and tasks for the current tenant. Use its prefilters to focus a dashboard on a building, an assignee, or a category of service requests, then open the corresponding tickets in [Service Desk](https://docs.buildings.ability.abb/collection/platform/service-desk.md).

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-8632911d56cd2ba776a4ad793e18a06737230f28%2Fticket-overview-counts.png?alt=media" alt="Ticket overview on a dashboard, showing priority counts, status groups, totals, and the All filters button"><figcaption><p>Review the filtered workload by priority and status.</p></figcaption></figure></div>

## Read the Overview

Open **Live Cockpit** **\[A]** and select the dashboard containing the widget.

The widget shows:

* Ticket counts for **Low prio**, **Medium prio**, and **High prio**.
* Ticket counts grouped as **Open/No tasks**, **In progress**, and **Completed/Closed/Canceled**.
* **Total tickets** and **Total tasks** for the configured filters.

Click a priority card, such as **High prio** **\[C]**, or a status row's arrow, such as **In progress** **\[D]**, to open the matching tickets in Service Desk. The widget's asset, assignee, reason, and tag filters are carried into that view.

## Configure Widget

You need access to add or edit widgets on the dashboard. See [Operating Widgets](https://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/operating-widgets.md) for the general widget controls.

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-65c7f66e1a1c7c6c2858fc7864c8f82ec99b1e09%2Fticket-overview-configuration.png?alt=media" alt="Ticket overview configuration with prefilters and the Allow to change filter setting"><figcaption><p>Configure the initial ticket scope and whether dashboard users can change it.</p></figcaption></figure></div>

1. Open the dashboard.
2. Click **Widget**.
3. Select **Ticket overview** on the **Builtin** tab.
4. Optionally select a **Primary asset (for title and alarms)**.\
   ◈ This identifies the widget's title and alarm context; use **Assets** **\[B]** under **Prefilter** to restrict the tickets.
5. Select the widget's **Width**.
6. Optionally enter a **Subtitle**.
7. Optionally enter a **Description**.
8. Set the initial filters under **Prefilter** using the reference below.
9. Enable or disable **Allow to change filter** **\[A]**.\
   ◈ Enable it when dashboard users should adjust the ticket scope. Disable it when they should only inspect the configured filters.
10. Click **Add Widget** **\[D]**.\
    ▷ The dashboard displays the summary for the configured filters.

The widget uses one combined presentation; there is no separate Small or Large variant. **Width** controls its space on the dashboard.

### Prefilter Reference

| Field               | Effect                                                                                                                       |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Assets** **\[B]** | Restricts tickets to the selected assets. Leave it empty for no asset restriction.                                           |
| **Assigned to**     | Restricts tickets to the selected assignees.                                                                                 |
| **Reason**          | Restricts tickets to the selected ticket reasons.                                                                            |
| **Tags** **\[C]**   | Restricts tickets by the selected tags. **All the selected required** uses AND logic; **One of the selected** uses OR logic. |

For example, select a building's assets and a service team member to monitor that person's workload for the building. Leave an optional filter empty when you do not want that restriction.

## Inspect or Change Filters

The callouts **\[A]** to **\[D]** in the overview figure refer to the dashboard, not the configuration dialog.

1. Click **All filters** **\[B]** on the widget.\
   ▷ If filter changes are enabled, **Change filters** opens. Otherwise, **All filters** displays the configured values read-only.
2. Adjust the filters in **Change filters**, if available.
3. If you changed the filters, click **Save** **\[E]**.\
   ▷ The widget refreshes its counts using the updated filters.

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-2328c0d409d7b1dd8f789208006080cd4a1bd838%2Fticket-overview-change-filters.png?alt=media" alt="Change filters dialog for Ticket overview with asset, assignee, reason, tag, and Save controls"><figcaption><p>Adjust the ticket scope without opening the full widget configuration.</p></figcaption></figure></div>

Use **Cancel** to discard changes. In the read-only dialog, use **Close** to return to the dashboard.


---

# 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://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/ticket-overview.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.
