> 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/faq/glpi/changes.md).

# Changes

***

### What is a change?

A **Change** is the establishment of the resolution of a Problem (in GLPI sense or not) or the establishment of a new material / human element or process of your IS[^1]. Change allows you to inform, assign, plan, budget, etc. The Changes are accessible in **`Assistance`** > **`Changes`**.

***

### How to create a change?

To create a Change, like any element of GLPI, click on **`add`**. The change form reminds the form of incidents, of which distinguish the concepts:

* requesters
* observers
* assigned
* status
* urgency
* impact
* priority
* category

Like the Problem, it is possible to attach other elements of GLPI to your Change: Ticket / Problem / Projects / Costs / etc.

A [procedure](/tutorials/helpdesk/changes.md) is available to help you implement your change.

***

### What is a reccurent change?

A reccurent change is a change that occurs periodically and is planned in order to prepare and plan the possible steps that could be linked to it.

{% hint style="success" %}
**Example :** Weekly check that Windows patches have no impact on production performance.
{% endhint %}

You can link other GLPI projects, problems, items, etc. to it.

***

### How do I create a reccurent change?

In **`Assistance`** > **`Reccurent changes`** click on **`Add`** Add a name and a comment if necessary. Set your change to active and indicate a start date (an end date if necessary). Add the desired periodicity as well as early creation if you want the change to be created before the **`start date`**. All that remains is to save your reccurent change.

{% hint style="success" %}
**Automatic actions**\
Remember to check that the **`RecurrentItems`** automatic action in **`setup`** > **`automatic actions`** is active and set to the correct **`run frequency`** so that the change creation action can be carried out.
{% endhint %}

***

### What status is available for changes?

The available statuses are :

| Status        |
| ------------- |
| New           |
| Evaluation    |
| Approval      |
| Accepted      |
| Pending       |
| Testing       |
| Qualification |
| Applied       |
| Review        |
| Closed        |
| Cancelled     |
| Refused       |

***

### Can changes be linked to other types of GLPI object?

Yes. It is possible to link problems, tickets, projects and elements of the fleet to have a complete overview of the progress of the change.

[^1]: Information Systems


---

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

```
GET https://help.glpi-project.org/faq/glpi/changes.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.