exemple : attaching a headset to a phone / rattacher un casque à un téléphone

Hallo,

I have a functionality suggestion that I believe would be easy to implement and make the Documents quite more flexible.

I would like to be able to add Author and User columns to the displayed items in the general view (i mean the overall screen displayed after clicking the Documents in the left Menu).

This would make the documents much more searchable.

Hi,

Problems and changes have Tme To Resolve fiend in the top area of pages

Maybe it will be usefull to have this field there in the Ticket 

InfiniBand doesn't seem to be supported at all in GLPI. InfiniBand ports in computers are wronlgly reported as "Ethernet" ports and when adding a new network connection, the selection of types doesn't include "InfiniBand". It would be great to have this in GLPI

For a tool which is also aimed at datacenters and full asset/infrastructure management, I would see it as a "must" to support InfiniBand. Should this maybe rather be posted as bug?

When the "Forgotten password" is clicked, GLPI generate and display a new password for the user.

Best practices who suggest to display a page for the user to choose a new password of his choice instead.

I would like to be able to quickly search in appliance. The current search system is quite time-consuming when we want to search by several columns. For me, the best solution would be to add filters such as those in the History tab. My question is: are there any plans to add this type of filtering? If not, could I get some tips on how I could add such filters to Appliance myself?

The Inventory SNMP agent's task only authorizes network or printer. 

It would be better to add UPS parameter to scan this specific object with relevant data instead of putting our UPS within the "Network" category only ro use SNMP scan.

Add support for glpi_agents - remote_addr inventory request.

For NAT based / VPN Network, public remote address could be used to contact agent, and request inventory.

in agent.php Agent::getAgentURLs(), Agent::guessAddresses() only retrieve URL based on glpi_networkports linked with computer, and not glpi_agents public address stored in glpi_agents remote_addr.

There's no oficial solution to deploy glpi on Kubernetes "k8s".

Related to: Feature Request: Container Image / General / GLPI (userecho.com)

I didn't see a place on the forum to suggest this but it would be really great if the restriction around not being able to post links on the GLPI forum had a white list of domains for the various GLPI domains like readthedocs.io etc so when posting a help request etc you can clear show where you got your information from.