My agency has left behind POP and IMAP protocols many years ago in favor of OWA and MAPI. Most contemporary (and unfortunately non-free) Service Desks do support native Exchange protocols. It would be amazing if these could be implemented in GLPI.

We use a reduce versión of the GUI for the final user. It´s posibble that dashboard plugin (https://forge.glpi-project.org/projects/dashboard/) come for default into the core for the final user?

For example, gather every computer in a group that has Google Chrome installed. Seems to be impossible at the moment (GLPI 10.0.17).

Hello, I would like to suggest an improvement in the location part of GLPI, which allows to define if a location can be related to a ticket or not. The goal is to force the user to choose the most specific location, especially when using multiple hierarchical levels of location, such as city > branch x > floor > room.

This would facilitate the management of tickets, avoiding that the user chooses a generic or incorrect location, and allowing to filter tickets by location more easily. It would also help to avoid unnecessary trips or surprises when attending a ticket in a certain location.

I believe that this functionality would be useful for many users of GLPI, and I hope that it can be implemented in a future version. 

Thank you for your attention.

#######################$$$

Título: Permitir definir se uma localização pode ser relacionada a um chamado ou não

Texto:

Olá, eu gostaria de sugerir uma melhoria na parte de localização do GLPI, que permita definir se uma localização pode ser relacionada a um chamado ou não. O objetivo é poder forçar o usuário a escolher a localização mais específica, em especial quando se utilizam vários níveis hierárquicos de localização, exemplo cidade > filial x > andar > sala.

Isso facilitaria o gerenciamento dos chamados, evitando que o usuário escolha uma localização genérica ou incorreta, e permitindo filtrar os chamados por localização mais facilmente. Também ajudaria a evitar viagens desnecessárias ou surpresas ao atender um chamado em uma determinada localização.

Eu acredito que essa funcionalidade seria útil para muitos usuários do GLPI, e espero que ela possa ser implementada em uma versão futura.

Obrigado pela atenção.

When the string of the item "Group in charge of the hardware" is too large, overlapping the item in the next column.

See the image below:

When reduce the font size by the browser the interface looks like this:

Add a different smtp server per entity in order to send email notification on différents domains.

For example: A common GLPI server for two companies with differents domains

Best regards

In addition to the top view of the server room, the possibility of seeing a complete row of racks, like the simple view of a rack but with all the storage.

I have not seen any tickets related to depreciation support. I really enjoy working with GLPI, but one of features that I think would be very useful is the incorporation of depreciation. Many ITSM projects incorporate some sort of straight line depreciation reporting. It looks like this was brought up in 2010 https://forum.glpi-project.org/viewtopic.php?id=21692

This would be a great feature in the Management field with either "Depreciation Rate" or set the rate based on asset type like "Computers - 5 year depreciation"

It would be nice to then pull reports on current assets values. Let me know if I'm missing some configuration, but based on my testing there is only currently Amortization support.

A computer (any type of asset) can be addressed through a unique url, something like http://localhost/glpi-9.2.4/front/computer.form.php?id=4150, where 4150 is the (unique, internal) id of the computer.

I'd like to use a url where the parameter is the inventory number (supposed unique)