> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/assistance/recurrentticket.md).

# Reccurent tickets

Recurring tickets allow you to schedule ticket creation for recurring events. For example :

* Open a ticket every Monday to check that weekend backup was correctly executed
* Open a ticket first day of the month to perform initialization operations

{% hint style="success" %}
You can use [templates ](https://help.glpi-project.org/documentation/modules/tabs/templates.md)to program recurrent ticket opening.
{% endhint %}

<figure><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2F2B4HAchN3PDTpJXeO5VP%2Fadd_recurrent_ticket.png?alt=media&amp;token=7b9e2afa-8d0f-4971-bd76-68202345e45c" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Reccurent ticket opening is done through an automatic action named **`RecurrentItems`**, see [Configure automatic actions](https://help.glpi-project.org/documentation/modules/configuration/crontasks.md).
{% endhint %}

## The different fields

* **Active**: allows to disable temporarily ticket creation;
* **Ticket template**: model that will be used for ticket creation;
* **Start date**: start date for ticket creation, mandatory;
* **End date**: optional, defines ticket creation end date;
* **Periodicity**: ticket creation period;
* **Preliminary creation**: time for anticipated ticket creation;
* **Calendar** : allows to limit ticket creation days;
* **Create a ticket per linked element.**

{% hint style="info" %}
Tickets will only be created if **`Active`** is **`Yes`** and if current date is between **`Start date`** and **`End date`**.
{% endhint %}

## The different tabs

### Informations

Displays the date and time of the next ticket creation.

***

### Historical

List the history of the recurring ticket.

***

### Items

You can add equipment to your recurring tickets. If the Create a ticket per linked element option is enabled, each piece of equipment will have its own ticket.

<a href="https://help.glpi-project.org/documentation/tabs/item.md" class="button secondary">Go to Items</a>


---

# 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://help.glpi-project.org/documentation/modules/assistance/recurrentticket.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.
