Enable the option of the autentication with Google, Github, Linkedin even twitter or Facebook.

Enable too Two Factor Auth support which includes SMS, email, phone calls, hardware, and software.

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.

---

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.

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.

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

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.

The idea would be to have unicity across itemtypes.

For example, an inventory number must be unique, whatever the itemtype.

wawax posted this idea to the project repository and tagged it as an enhancement.

It would be very useful to be able to place links in an article in the knowledge base, that lead to another place in the same article. This would make it easier to navigate through a long article, or even to make a table of contents.

It is really hard to learn how GLPI works. The business model is complicated, and all the documentation is english or french is deprecated 

Adjust GLPI to TISAX certificate and ISO/IEC 27001 requirements.

GLPI is in 80% inline with TISAX requirements.

Will be super useful for all companies what have to implement TISAX and they already using GLPI.

Tthere is only few point missing in GLPI to be TISAX compliance, like:

E-learing platform

Risk assessments