Please check if the feature has not already been requested.
If not, please describe it

GLPI + AI Bot
Enable an artificial intelligence bot chat in the GLPI that take and give responses of the Knowledge Base and the information into the tickets

Comparison of two assets side by side to findout duplicates
After some searching you discover this asset may be a duplicate of an other. Added by someone despite it already exists, or imported twice by an automatic inventory tool.
To ease comparison between two assets, GLPI should display them in a single page, side by side and show differences. Three buttons would help to solve the "conflict" : merge, delete A or delete B.

Surbrillance des onglets sélectionnés
Bonjour,
En 0.90.1, les onglets sélectionnés de la timeline sont blancs. Ce qui est particulièrement perturbant quand on se trouve sur le premier onglet de la timeline. Exemple :
Dans cet exemple, on ne sait pas si c'est l'onglet "Réservation" ou "Administration" qui est sélectionné.
Pouvez-vous faire en sorte que la couleur de fond du dernier élément du fil d'Ariane (ici le rouge de "Réservations") soit celle de l'onglet sélectionné (ici "Réservation") quel que soit le thème ?
La demande est la même pour permettre de distinguer les onglets sélectionnés dans :
- les marque-pages (voir capture d'écran)
- les tickets (voir capture d'écran)
Merci

Projects - add more specific permission configuration for management
I'm using GLPI and the project function for organizing our plan, but everyone who has the project permission can control or modify everything in project.
For more flexible managing, the GLPI provides more specific permission configuration is a better choice.

Implementation of Proximity Search Criteria in GLPI
English:
Title: Implementation of Proximity Search Criteria in GLPI
Description: Taking advantage of the geolocation capabilities in GLPI and its integration with the OpenStreetMap API, I suggest analyzing the feasibility of implementing a search criterion that allows identifying tickets within a radius or road distance of X km from a selected location or the current location determined by GPS. This feature would be extremely useful to optimize technicians' time, especially when they are traveling to remote areas to resolve incidents. By enabling the advancement of other tickets in the region, the efficiency and utilization of time would be significantly improved.
Benefits:
1. Time Optimization: Technicians can anticipate services while traveling.
2. Efficiency in Service: Reduction of idle time and increase in completed tickets.
3. Improvement in Ticket Management: Better resource allocation and ticket prioritization.
4. Customer Satisfaction: Reduction in waiting time for problem resolution.
Sugestão de Melhoria para o GLPI: Critério de Busca por Proximidade
Português:
Título: Implementação de Critério de Busca por Proximidade no GLPI
Descrição: Com a possibilidade de geolocalização das localizações no GLPI e a integração da API do OpenStreetMap, sugiro analisar a viabilidade de implementar um critério de busca que permita identificar chamados dentro de um raio ou distância rodoviária de X km de uma localidade selecionada ou da localização atual determinada por GPS. Essa funcionalidade seria extremamente útil para otimizar o tempo dos técnicos, principalmente quando estão se deslocando para áreas remotas para resolver incidentes. Ao possibilitar o adiantamento do atendimento de outros chamados na região, a eficiência e a utilização do tempo seriam significativamente melhoradas.
Benefícios:
1. **Otimização do Tempo**: Técnicos podem antecipar atendimentos enquanto estão em deslocamento.
2. **Eficiência no Atendimento**: Redução de tempo ocioso e aumento de atendimentos concluídos.
3. **Melhoria na Gestão de Chamados**: Melhora na alocação de recursos e priorização de chamados.
4. **Satisfação do Cliente**: Redução do tempo de espera para resolução dos problemas.
---

Used item history unavailable from User view
When an item is being assigned to a person, it shows up under "Used items" list in person view, but there's no entry about used items under person's historical view. On the other hand, if an asset's history is being viewed, history tab shows the history of users to whom the asset was/is assigned to.
This would enable to track what has been ever assigned to user during the user's whole GLPI lifecycle, also this would enable a lot easier tracking of assets - for example assets were assigned to someone else by mistake or by somekind of automation mistake. Currently one has to know the asset name/number first.

add feat: approval chain: sequential approval
Hello.
It would be great if you made consistent approval in the business rules for tickets.
example:
an application was created / approver #1, then if approver #1 approved, then the ticket was transferred to approver #2, etc.

Signaturepad in GLPI
Hello would it be possible to add a signature pad in jquery that can be used to confirm assignement of assets to a user ?

The ability to combine/merge items into one.
One typical problem situation is when a department in a company first manually enters equipment(computer, mice, monitors, usb devices,printers, network devices, simcards, phones, etc) from orders and then there is a record completed by an agent whether GLPI or Fusioninventory.
Everything is ok until the wrong serial number is entered in the manually entered record (or the numbers are entered from the typist's head :/).In such a case we have a problem because 2 separate items begin to function in GLPI , one entered manually with important accounting and administrative data and the history of their changes and the other entered by the agent with technical IT data.
There is no possibility in such a case to merge them into one correct record with preservation of the history of changes.
With preservation of changes also in the fields added using the fields plugin.
Customer support service by UserEcho