> For the complete documentation index, see [llms.txt](https://docs.dailybiz.com/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dailybiz.com/index/crm-crm/contacts-and-evenements/recherche-and-creation/actions/ticket.md).

# Ticket

## **Historique**

L'historique dans les tickets permet de suivre tous les changements de statut d’un ticket étape par étape.\
\
Chaque fois qu’un ticket passe à un nouveau statut comme "Créé" "Pris en charge" "En attente" "Résolu" ou "Clos" une ligne est ajoutée avec la date l’heure et le nom de la personne qui a effectué l’action.\
\
Par exemple si un ticket est créé puis immédiatement pris en charge puis mis en attente en attendant une réponse du client l’historique affichera ces trois étapes dans l’ordre.\
\
Même si le ticket repasse par un statut déjà utilisé cela sera enregistré à nouveau ce qui permet de ne rien perdre et d’avoir une traçabilité complète.


---

# 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.dailybiz.com/index/crm-crm/contacts-and-evenements/recherche-and-creation/actions/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.