> 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/tickets/configure-ticket.md).

# Configure ticket

## Overview

<figure><img src="/files/8a93435fc9951299870b7957bdfbde1ae3a40187" alt=""><figcaption></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="100.33333333333337"></th><th width="206"></th><th width="634"></th><th></th></tr></thead><tbody><tr><td><strong>[A1]</strong></td><td>User name</td><td>Your user name will be filled in by default.</td><td>Optional</td></tr><tr><td><strong>[A2]</strong></td><td>Phone number</td><td>If a phone number is stored, it will be filled in automatically.</td><td>Optional</td></tr><tr><td><strong>[A3]</strong></td><td>Email</td><td>The email address of your user will be entered automatically.</td><td>Optional</td></tr><tr><td><strong>[B]</strong></td><td>Assigned to</td><td>Assign the ticket to a user.</td><td>Required field</td></tr><tr><td><strong>[C]</strong></td><td>Ticket title</td><td>Give the ticket a title.</td><td>Required field</td></tr><tr><td><strong>[D]</strong></td><td>Priority</td><td>Set the priority of the ticket.</td><td>Required field</td></tr><tr><td><strong>[E]</strong></td><td>Reason</td><td>Select the reason for the ticket.</td><td>Required field</td></tr><tr><td><strong>[F]</strong></td><td>Alarm</td><td>Assign the ticket to a specific alarm. <br>If you <a href="/pages/4b379c335a3623de2586cc693554a46f063b1111#ueber-einen-alarm-erstellen">-> created ticket via an alarm</a> have done so, this field is already filled in.</td><td>Optional</td></tr><tr><td><strong>[G]</strong></td><td>asset</td><td>Assign an asset to the ticket to associate it with specific devices or systems.</td><td>Optional</td></tr><tr><td><strong>[H]</strong></td><td>Tags</td><td>Choose whether the tags from the asset or custom tags should be used.</td><td>Optional</td></tr><tr><td><strong>[H1]</strong></td><td>Search tags</td><td>Assign tags to better categorize the ticket and manage access rights.</td><td>Optional</td></tr><tr><td><strong>[I]</strong></td><td>Description</td><td>Add a description to explain the reason for creating the ticket.</td><td>Required field</td></tr><tr><td><strong>[J]</strong></td><td>Template</td><td>Mark this ticket as a template for future tickets if desired.</td><td>Optional</td></tr><tr><td><strong>[K]</strong></td><td>Attachments</td><td>Upload documents such as datasheets or technical documentation.</td><td>Optional</td></tr><tr><td><strong>[L]</strong></td><td>Save</td><td>Save the ticket and create it.</td><td>-</td></tr></tbody></table>

## Step by step

1. Follow the steps in chapter [-> Create tickets](/collection/english-v14/documentation/tickets/create-tickets.md) from
2. Configure the ticket. At least the fields **\[A]**, **\[F]** and **\[H]** must be filled in&#x20;
3. Click on **Save \[E]**\
   ▷ The menu [-> Ticket details](/collection/english-v14/documentation/tickets/ticket-details.md) opens
4. Continue in the chapter [-> Create tasks](/collection/english-v14/documentation/tickets/create-tasks.md)&#x20;


---

# 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/tickets/configure-ticket.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.