> 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/ticket-konfigurieren.md). # Configure ticket The same form is used when creating and editing a ticket. When editing, the final action is **Save**, when creating **Create ticket \[M]**.

Formular zum Erstellen und Konfigurieren eines Tickets — Create and configure ticket

Element	Title	Description
[A1]	Name	Reporter name. Taken from the user profile and can be adjusted. Optional.
[A2]	Phone number	Reporter phone number. Optional.
[A3]	Email	Reporter email address. Optional.
[B]	Title	Meaningful title of the ticket.
[C]	Priority	Priority Low, Medium or High.
[D]	Assignee	Person who processes the ticket. A default person defined in the settings is preselected.
[E1]	Due type	Choose a fixed date or a period.
[E2]	Due date	Date or start and end date of the period.
[F]	Asset	Assigned asset. Optional.
[G]	Reason	Reason or category of the ticket.
[H1]	Tag source	Uses asset tags or a custom selection. Optional.
[H2]	Tags	Assigns tags for categorization and access control. Optional.
[I]	Associated alarm	Links the ticket to an alarm. When created from an alarm, the field is prefilled. Optional.
[J]	Reference number	Freely definable external reference number. The input is validated. Optional.
[K]	Description	Detailed description of the work order.
[L]	Attachments	Select files or drag them into the area. Optional.
[M]	Create / Save ticket	Creates the ticket or saves the changes.

After creation, the [-> Ticket details](/collection/english-v14/documentation/tickets/ticket-details.md). Create at least one [-> task](/collection/english-v14/documentation/tickets/tasks-erstellen.md), so that the ticket can be closed later. --- # 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/english-v14/documentation/tickets/ticket-konfigurieren.md?ask=&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.