It will be nice to have possibility to sort tickets by fields on "Tickets" tab for assets elements or users. See attachment :

To exploit the knowledge base at best when processing a ticket, depending on its type and category , it will be a good KB list is proposed to the technician to solve the problem without going to perform research itself in the knowledge base.

If any of KB self- proposed resolution allows the ticket, that acquires a point scoring KB making it more relevant. This KB will be offered in the first position the next time a ticket of the same qualification will be open.

This feature will :

-> To save time technicians
-> From more easily create KB if none is proposed in qualifying ticket
-> Prioritize the most important KB

When the user approves the solution of the ticket, the message appears in the lower field must tell the user "Now click this link and answer the ticket satisfaction survey ."

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

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

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.

---

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.