When a user is reaching the satisfaction survey screen, the rating field is defaulted to 3 stars. Many of our users leave this field to 3 stars instead of providing a real rating. I think it would make more sense to have no default on this field to force the user to provide a relevant rating on his own.

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.

It would be useful to be able to link multiple groups to an asset.

There are cases where multiple teams use an asset and having this possibility would be useful as we could have visibility of which assets a group uses and vice versa which groups use an asset. For example, during maintenance interventions, I can see who uses the asset and notify only those groups.

UPS managment needed whith specifications of this device type and can connection to PC, monitors, ethernet devices (as additional tab in asset page), and can be added to rack managment

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:

Importing assets directly from Intune (Microsoft Endpoint Manager) would be beneficial. A connector could grab this information via the MS Graph API. Intune has already lots of data about the asset like main user or serial number, hardware type and information like ram, disk etc. thx! 

Create new options on schedule in recurrent tickets, e.g.

"Create ticket in the last friday of the month"

"Create ticket in the second thursday of the month"

Have the ability to manage in profile configuration so that standard users (who have the simplified profile interface) can see changes, problems, and projects. (ITIL object) Without being able to modify.

Would be nice if we could transfer Component Items (e.G. Simcards) between entities or at least between Components in different Entities.

Modify active directory user information directly from glpi, unlock account or reset password can be vert Helpfull  for  helpdesk user.