# Creating Templates for Tickets

## Add templates

Templates can simplify user requests by pre-filling fields, hiding some or forcing certain fields to be filled in.

In our example, we'll create an incident template to help users report incidents correctly.

* From **`configuration`** > **`titles`** > **`ITIL category`**, select your category
* Click on **`incident template`**.
* Enter the name of your template
* Close the template creation confirmation window, then click on de **`template for an incident`**.
* Select the newly created template

![Alt text](/files/bWuhUrduE6R5uvkXNpbY)

***

### Mandatory fields

You can add mandatory fields for the simplified interface and/or the standard interface. They will be marked with a

In our example, we're going to force the user to fill in the **`description`** and the **`emergency`**.

* Select description from the drop-down list, then **`add`**.
* Do the same with **`emergency`**.

![Alt text](/files/JhKaqoiESGteYmFn2G8D)

***

### Predefined fields

To guide your users, you can pre-fill fields to make the interface more interactive. This will give you as many elements as possible to help you resolve the incident. In our example, we'll fill in the description field to make it as complete as possible.

* In the **`predefined fields`** tab, select **`description`**.
* Fill in the information you deem necessary
* Click on **`add`**

![Alt text](/files/0Z0YQMOOOKj1WQp4bTNp)

***

### Hidden fields

Hidden fields avoid overloading the user interface and simplify the writing of the incident.

* In the **`hidden fields`** tab, add the fields you don't want to appear in the standard and/or simplified interface.
* Click on **`add`**

![Alt text](/files/orC77yXqWGIXNpaxOjFc)

***

### Preview

You can view the rendering of the simplified and standard interface in the corresponding tabs

***

### ITIL Category

The "ITIL category" tab lets you see which category your template is available in.

![Alt text](/files/00djHCbHfRdlbDzxBqC9)

You can add different templates for each type of category (request, incident, change, problem). You can also use the same template for several category types.

## Link your template to your category

{% hint style="info" %}
**Note**

If you want to know more about categories, you can use [this article](#itil-category)
{% endhint %}

* From **`configuration`** > **`titles`**, select the relevant category
* In the field for which you want your template to appear, select it from the drop-down list
* Click on **`save`**.

![Alt text](/files/S1hvpqKYinswn3Ol7dYf)

From now on, when a user selects the ITIL **`mailbox`** category, the template will be selected.

![Alt text](/files/coHMhz1byXMHBoQAEO0m)

{% hint style="success" %}
**Insert `description`**

As we have forced the description insert to be filled in, if the user leaves it as it is, an error message will appear forcing them to change the default values

<img src="/files/EKoJsmWlADAWkPOKVzch" alt="" data-size="original">
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.glpi-project.org/tutorials/helpdesk/create_templates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
