> 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/english-v14/documentation/widgets/predefined-widgets/ticket-overview.md).

# Ticket overview

The ticket overview displays tickets and tasks for the current project.

<div data-full-width="true"><figure><img src="/files/0b173a3f5cfd1238597ac1f55159e5ff6c4d171e" alt=""><figcaption><p>The "Ticket Overview" widget</p></figcaption></figure></div>

## Configure widget

{% @supademo/embed demoId="gu5ZEnPWhi8TdA02U6xNr" url="<https://app.supademo.com/demo/gu5ZEnPWhi8TdA02U6xNr>" fullWidth="true" %}

1. Make sure you are in the "Dashboard" menu
2. Click "Add widget"
3. Click on "eliona"
4. Click on "Ticket Overview"
5. Select the primary asset. The name of this asset will appear in the widget title bar.
6. Optional: Choose how much space your new widget should take up on the dashboard.
7. Click "Add widget"
8. The widget appears on 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets/predefined-widgets/ticket-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.