# Problems
A problem is the cause of potential incidents and, once identified, can be managed in GLPI.
Creating a problem object can be done either from the ticket form, in tab *Problem*, or directly from menu *Assistance > Problems*.
The problem creation form is very similar to the ticket creation form and shares with it many concepts: `Requester`, `Watcher`, `Assigned to`, `Status`, `Urgency`, `Impact`, `Priority`, `Category`. For more information, see [Manage tickets](/documentation/modules/assistance/tickets/ticketmanagement.md).
{% hint style="info" %}
Check what is means From tickets list, an alternative solution can be associated to linked tickets without solving the problem. Depuis la liste des tickets, une solution de contournement peut être associé massivement aux tickets liés sans pour autant résoudre le problème.
{% endhint %}
Problems use their own notifications, see [configuration of email follow-ups](/documentation/modules/configuration/notifications/email_notifications.md).
Statistics similar to tickets are available for problems, see [Display statistics](/documentation/modules/assistance/statistics.md).
## The different tabs
### Analysis
This tab contains problem analysis.
It consists of 3 inserts:
* Impacts
* Causes
* Symptoms
***
### Statistics
Statistics similar to tickets are available for problems.
Go to Statistics
***
### Tickets
List all tickets are linked to the problem. You can add a new ticket or link an existing ticket.
Go to Tickets
***
### Changes
This tab allows to display changes associated with the problem and add new changes.
Go to changes
***
### Costs
The cost represents the financial impact of the problem encountered. It can be human, material or fixed.
{% hint style="warning" %}
A cost cannot be added once the issue has been closed or resolved.
{% endhint %}
Go to Costs
***
### Projects
You can attach or add one or more projects to your problem.
Go to Projects
***
### Items
This tab allows to attach an item to the problem by choosing the type and the selected item.
Go to Items
***
### Impact analisys
Impact analysis enables you to visualise the impact of failures on an entire infrastructure.
Go to Impact analisys
***
### 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
***
### Knowledge Base
You can link an article from the knowledge base.
Go to Knowledge base
***
## 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/problems.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.