# 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](https://help.glpi-project.org/documentation/modules/assistance/tickets/ticketmanagement). 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](https://help.glpi-project.org/documentation/modules/tools/projects)).

Changes use their own notifications (see [configuration of email follow-ups](https://help.glpi-project.org/documentation/modules/configuration/notifications/email_notifications)).

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

<div align="left"><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2FFTcwzBK4dqXGZeX3756r%2Fstatus_change.png?alt=media&#x26;token=c3faa418-f56f-4d46-98c3-67986a1163de" alt="Change status"></div>

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

![View changes analysis](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Fgit-blob-93caeab08a7d3f87bdaecf3bc6c3a37900116bbe%2Fchanges-delete.png?alt=media)

{% 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.

<div align="left"><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Fgit-blob-c5808a9c414a278bd6e575ae05e1aae14f4c299a%2Fchanges-analysis.png?alt=media" alt="View changes analysis"></div>

### Plans

This plan contains :

* Deployment plan
* Backup plan
* Checklist

<div align="left"><img src="https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Fgit-blob-b7f149a9fd1e14b6dac433fb21ae15175debb499%2Fchanges-plans.png?alt=media" alt="View changes plans"></div>

***

### Statistics

The statistics are intended to provide information, showing how long it takes to take over, close a change, etc. Statistics similar to tickets

<a href="statistics" class="button secondary">Go to Statistics</a>

***

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

<a href="broken-reference" class="button secondary">Go to Approvals</a>

***

### Cost

Costs can be linked to the budget in order to estimate whether an expense will fit within the allocated budget.

<a href="../../tabs/cost" class="button secondary">Go to Costs</a>

***

### Projects

This tab allows to attach a project to the change and displays already attached projects.

<a href="../../tabs/projects" class="button secondary">Go to Projects</a>

***

### Problems

Changes may be due to problems. In this tab, you can link a problem to your change.Tickets

<a href="../../tabs/projects" class="button secondary">Go to Problems</a>

***

### Changes

A change may have been introduced via a ticket. In this tab you can attach the ticket(s) affected by the change.

<a href="../tabs/changes" class="button secondary">Go to Changes</a>

***

### Tickets

List all tickets are linked to the problem. You can add a new ticket or link an existing ticket

<a href="../../tabs/tickets" class="button secondary">Go to Tickets</a>

***

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

<a href="../../tabs/item" class="button secondary">Go to Items</a>

***

### Impact Analysis

Impact analysis allows you to create diagrams of your infrastructure and see the impact of a change on it.

<a href="../../tabs/impact_analysis" class="button secondary"> Go to Impact analysis</a>

***

### Knowledge base

The *Knowledge base* tab is used to show or add linked knowledge base articles.

<a href="../../tabs/knowledgebase" class="button secondary">Go to Knowledge base</a>

***

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

<a href="../../tabs/notes" class="button secondary">Go to Notes</a>

***

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