Add the possibility to archive an item.

An archive is a new state, as it is for deleted items.

The simple way is to add a is_archived field, and filter the view in the asset's search engine.

In 0.90.1, when a task has "To do" status, a empty box represents this status.

I will be nice to change status from "To do" to "Done" with a click on empty box (and vice-versa).

Currently it is possible to add/link ticket only to computer (host) even though it's possible to list virtual machines (guests) underneath. It would be great to add/link tickets to those virtual machines (guests).

For example it could be valuable to know how many tickets/troubles are related to which particular virtual machine when looking for repeating problems, problematic VMs and similar.

Hosts could be mixed with Linux/Windows VMs and each of them could be managed be different person so assigning tickets just to host is not enough.

A few years ago you added the possibility of being able to inventory the meshcentral, today it could be done with rmm, but in these years I have not seen that when it is detected if there is a remote management, it takes the hyperlink, since it is not a standardized link, So what I know is possible is through external links to put our administration and remote management page and pulling the data from the "$id" field that you generate in Item_RemoteManagement.php, since I wanted to do the same with the RMM but this It disappears because I don't know, so the most viable thing is to insert our page through external links: example:
https://mesh.net/?viewmode=11&hide=31&gotonode=$id

As you can see here, the meshcentral has the link enabled so I edited Item_RemoteManagement.php, but this becomes cumbersome because every time there is an update it is lost and I have to reconfigure it

Hello,

I am a user of GLPI and I would like to suggest a new feature for version 10: the management of service routes.

This feature would allow fleet managers to plan, optimize and monitor the routes of vehicles and drivers, taking into account factors such as the customer's address, time constraints, tolls, traffic conditions and necessary breaks.

The benefits of this feature would be:

• Cost reduction: route optimization could reduce fuel consumption, vehicle wear and tear, and driver travel time.
• Increased productivity and quality of service: managers could ensure that services were performed in a timely manner and to the expected quality.
• Improved customer and driver satisfaction: customers would be satisfied with the faster and more efficient service, and drivers would be satisfied with the reduced travel time and increased safety of the routes.

The feature could be integrated with the ticket module, so that managers could assign tasks to drivers, track the status of services and generate performance reports. In addition, the feature could be compatible with navigation apps, such as Google Maps or Mapbox, to facilitate driver guidance on routes.

Here are some additional features that the feature could have:

• The ability to relate multiple tickets to a route, in order to group services by proximity, priority or other criteria.
• A route scheduling system, integrated with the GLPI scheduling system, so that managers could define the dates and times of the routes, as well as the time windows for each service.
• The ability to approve routes, so that managers could validate the routes proposed by the system or make manual adjustments, if necessary.
• The definition of technicians, vehicles, the number of seats in the vehicle and other resources needed for each route, in order to ensure the efficiency and safety of operations.

I believe that this feature would be a valuable addition to GLPI, as it would contribute to the improvement of the efficiency and quality of the services provided by companies.

Sincerely,

Eduardo Spinola

Olá,

Sou um usuário do GLPI e gostaria de sugerir uma nova funcionalidade para a versão 10: o gerenciamento de rotas de atendimento.

Essa funcionalidade permitiria aos gestores de frotas planejar, otimizar e monitorar as rotas dos veículos e dos motoristas, levando em conta fatores como o endereço do cliente, as restrições de horário, os pedágios, as condições de tráfego e as pausas necessárias.

Os benefícios dessa funcionalidade seriam:

• Redução de custos: a otimização das rotas poderia reduzir o consumo de combustível, o desgaste dos veículos e o tempo de deslocamento dos motoristas.
• Aumento da produtividade e da qualidade dos atendimentos: os gestores poderiam garantir que os atendimentos fossem realizados no tempo adequado e com a qualidade esperada.
• Melhoria da satisfação dos clientes e dos motoristas: os clientes ficariam satisfeitos com o atendimento mais rápido e eficiente, e os motoristas ficariam satisfeitos com a redução do tempo de deslocamento e a maior segurança das rotas.

A funcionalidade poderia ser integrada com o módulo de tickets, para que os gestores pudessem atribuir as tarefas aos motoristas, acompanhar o status dos atendimentos e gerar relatórios de desempenho. Além disso, a funcionalidade poderia ser compatível com aplicativos de navegação, como o Google Maps ou o Mapbox, para facilitar a orientação dos motoristas nas rotas.

A seguir, são apresentadas algumas características adicionais que a funcionalidade poderia ter:

• Possibilidade de relacionar vários tickets a uma rota, de forma a agrupar os atendimentos por proximidade, prioridade ou outros critérios.
• Sistema de agendamento de rotas, integrado ao sistema de agendamento do GLPI, para que os gestores pudessem definir as datas e os horários das rotas, bem como as janelas de tempo para cada atendimento.
• Possibilidade de aprovação das rotas, para que os gestores pudessem validar as rotas propostas pelo sistema ou fazer ajustes manuais, se necessário.
• Definição dos técnicos, dos carros, do número de vagas no carro e de outros recursos necessários para cada rota, de forma a garantir a eficiência e a segurança das operações.

Acredito que essa funcionalidade seria uma valiosa adição ao GLPI, pois contribuiria para a melhoria da eficiência e da qualidade dos atendimentos prestados pelas empresas.

Atenciosamente,

Eduardo Spinola

By default storage devices like NetApp,Synology, Dell EMC are detected as Network devices, and it is not possible to see the disk usage, CPU and Memory usage. It would be nice to have it and be able to manage.

business rules : add new criterion "Technician - User DN" with "regular expression matches"

Because with the "user DN" of the Active Directory together with regular expressions it gives you enormous power to customize various rules