Il serait pratique de colorer une tâche dans le calendrier en fonction de la priorité du ticket auquel elle est associée

I think that multi chronometer for tasks. The intension is a better control
of task. Multi tasks running at the same time. exemple Stop the task 1 e
continue the task 2.

Some times the user call e dont have ticket. I could start the chronometer
and when stop i would have the option to create a ticket.

It would be beneficial to create custom user profiles in GLPI based on departments and assign permissions to different entities.

(This example is very simplified)

Example:

1. User Profiles:

   • IT Department
   • HR Department
   • Finance Department
   • Marketing Department

2. Permissions:

   • Tickets
   • Assets
   • Projects

3. Entities:

   • IT Entity
   • HR Entity
   • Finance Entity
   • Marketing Entity

Permission Matrix:

Collaborative Projects:

Explanation:

• IT Entity: IT and Finance departments collaborate on Project A.
• HR Entity: HR and Marketing departments collaborate on Project B.
• Finance Entity: IT, Finance, and Marketing departments collaborate on Project C.
• Marketing Entity: Marketing, HR, and IT departments collaborate on Project D.

Benefits:

• No need to switch profiles.
• All information is available in one view.
• Users see only the departments and entities where they have permissions.
• Simplifies workflow and improves efficiency.
• Enhances collaboration by allowing multiple departments to share permissions within the same entity.

With templates, you can set rules for defining items like tickets or assets. Applying this to profile customization in GLPI allows users to work within the full structure of the root entity but only see departments and entities where they have permissions. This avoids the need to change profiles to work in different departments.

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 using a ticket, I want to assign some consumables to it and have them be adjusted in the consumables panel.

So, if I have a printer that the team submitted a ticket for more ink, 

1. I go into the ticket
2. click a new "consumables" tab
3. Add the consumables to the ticket (just like items, only with the extra "consumables" data like who it's assigned to)
4. The inventory in consumables changes to reflect the ink that was used.

When creating a dashboard, could we possibly be able to integrate "saved search" results as widgets ?
Thanks in advance

Lorsque nous créons des "tableaux de bord" (ou 'dashboard'), peut-on imaginer une possibilité d'intégrer les résultats des "recherches sauvegardées" sous forme de widgets ?
Merci par avance

Please add variables to the ticket template. Such as the time and date in the title and description field

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.

I suggest adding the option to add a floorplan to graphically show the location of the PCs. I share an example:

The display of pc's in the form of list is great. But I think that an ideal complement would be to provide the application with the ability to visualize the location of the devices on a floorplan.