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

# Configure Ticket

## Overview

<figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FBT0RMnN6AkPKOhVBM9qY%2FTicketing%20(6).png?alt=media&#x26;token=f9ce171e-9bb2-4d85-b621-0e4169c3b5eb" alt=""><figcaption></figcaption></figure>

<table data-full-width="true"><thead><tr><th width="74.73332722981775"></th><th width="170"></th><th width="634"></th><th></th></tr></thead><tbody><tr><td><strong>[A1]</strong></td><td>User Name</td><td>Your user name is 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 is automatically filled in.</td><td>Optional</td></tr><tr><td><strong>[A3]</strong></td><td>E-mail</td><td>The email address of your user is automatically entered.</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>Title of the ticket</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="/collection/platform/service-desk/create-tickets.md">-> created the ticket</a> via an alarm, this field is already filled out.</td><td>Optional</td></tr><tr><td><strong>[G]</strong></td><td>Asset</td><td>Assign an asset to the ticket to link it to specific devices or systems.</td><td>Optional</td></tr><tr><td><strong>[H]</strong></td><td>Tags</td><td>Choose whether to use tags from the asset or custom tags.</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 data sheets or technical documents.</td><td>Optional</td></tr><tr><td><strong>[L]</strong></td><td>Save</td><td>Save and create the ticket.</td><td>-</td></tr></tbody></table>

## Step by Step

1. Follow the steps from the chapter [-> Create Tickets](/collection/platform/service-desk/create-tickets.md)
2. Configure the ticket. At least the fields **\[A]**, **\[F]**, and **\[H]** must be filled out.
3. Click on **Save \[E]**\
   ▷ The menu [-> Ticket Details](/collection/platform/service-desk/ticket-details.md) opens
4. Continue in the chapter [-> Create Tasks](/collection/platform/service-desk/create-tasks.md)


---

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