# Changes
A change is a modification of the information system's infrastructure.
A change can be created either from a ticket form or a problem form, in tab **Changes**, or from menu **`Assistance` > `Changes`**.
The form to create a change is similar to the ticket creation form and shares with it many terms: *requester*, *watcher*, *assigned to*, *status*, *urgency*, *impact*, *priority*, *category*. For more information see [Manage tickets](/documentation/modules/assistance/tickets/ticketmanagement.md). The validation process is also the same as tickets in order to allow preliminary validation of the change (tab *Validations*).
Once the change is created, it is possible to attach tickets but also impacted items (tab *Items*). An analysis phase (tab *Analysis*) consists in describing impacts and controls list in order to implement this change through a deployment plan, a backup plan and a checklist (tab *Plans*).
Same as tickets, task, costs and solution allow to follow and solve the change. For complex changes management, a change can be linked with one or several projects allowing a mode detailed management ([Manage projects](/documentation/modules/tools/projects.md)).
Changes use their own notifications (see [configuration of email follow-ups](/documentation/modules/configuration/notifications/email_notifications.md)).
## Add a change
* To add a new change, click on **+ Add** at the top of the screen
* Fill in the various tabs of your change to make it as complete as possible
### Status
Several statuses are available, including some for test phases, validation, qualification, etc.
## Delete a change
* To delete a change, click on the change concerned
* Click on put in trashbin at the bottom of the screen
## Restore or delete permanently
* To delete or restore a change, click on the trashbin (at top right of screen)
* Select the change concerned
* Click on **Actions**
* Select **Restore** or **Delete permanently**
* Click on **Post**
{% hint style="danger" %}
**Delete permanently** remove definitively the change, you won't be able to get it back.
{% endhint %}
***
## The different tabs
### Analysis
This tab contains :
* Impacts
* Control list in order to implement the change.
### Plans
This plan contains :
* Deployment plan
* Backup plan
* Checklist
***
### Statistics
The statistics are intended to provide information, showing how long it takes to take over, close a change, etc. Statistics similar to tickets
Go to Statistics
***
### Approvals
Approval allows you to send requests to groups and/or users (or certain users within a group) in order to obtain their validation of the change in question. You can see Approvals for more information.
Go to Approvals
***
### Cost
Costs can be linked to the budget in order to estimate whether an expense will fit within the allocated budget.
Go to Costs
***
### Projects
This tab allows to attach a project to the change and displays already attached projects.
Go to Projects
***
### Problems
Changes may be due to problems. In this tab, you can link a problem to your change.Tickets
Go to Problems
***
### Changes
A change may have been introduced via a ticket. In this tab you can attach the ticket(s) affected by the change.
Go to Changes
***
### Tickets
List all tickets are linked to the problem. You can add a new ticket or link an existing ticket
Go to Tickets
***
### Items
#### Link a device
You can attach any item from the list below:
* Computer
* Database
* Device
* Enclosure
* Monitor
* Network device
* Phone
* Printer
* Rack
* Server room
* Software
Go to Items
***
### Impact Analysis
Impact analysis allows you to create diagrams of your infrastructure and see the impact of a change on it.
Go to Impact analysis
***
### Knowledge base
The *Knowledge base* tab is used to show or add linked knowledge base articles.
Go to Knowledge base
***
### Notes
The *Notes* tab provides a free text field for storing additional information. Notes are displayed in the order of their creation. You can also add a document.
Go to Notes
***
### History
The *History* tab is used to show any changes made to an item. The following information about the changes is available:
* ID of the change.
* Date and time the change was made.
* User who made the change. If this field is not filled, it means that the action was done automatically (For example: automatic inventory update).
* Field that was changed.
* Description of the change that was made.
The description of the change represents either the difference between the old and the new value (For example with location field: Change HQ to Remote Office A), or the explanation of the action which was carried out (For example: Uninstallation of a software: "Gimp 2.0").
{% hint style="info" %}
For dropdowns or objects with a parent/child relationship, the modification of a child will appear in the history of the parent element.
{% endhint %}
***
### All Information
For an item, all information is displayed on one page from the *All* tab. This shows all of the tabs of an object's form in one view, one below the other.
---
# 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/documentation/modules/assistance/changes.md?ask=
```
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.