I would like to request support for detailed printer page counters by paper size in GLPI. Currently, only counters like copyblack_a3 and copycolor_a3 are supported, but I need counters for other paper sizes (e.g., PRINT_A4, PRINT_A5, PRINT_FOLIO, etc.) for both printing and copying functions.

This feature was discussed in the GLPI Agent GitHub repository, where I provided snmpwalk data for a Kyocera TASKalfa 3011i printer, and it was confirmed that GLPI Agent can collect this data, but GLPI itself requires a significant update to support it. Here is the link to the discussion: https://github.com/glpi-project/glpi-agent/discussions/913 (note: the issue may have been moved to "Discussions" by the time you read this).

I believe this feature would be useful for many users who need detailed tracking of printer usage by paper size.

Add option to assign entities to groups(regions, routes or something) or add field 'location' to entities to sort ticket for easily plan route for car (technician).

We have many customers (200, one customer-one entity) and always 100+ opened tickets.

Searching and planing tickets from one region(route) is hard. There is no easy way to select ticket from one region(location) to plan best way for car/technician.

We need to be able to customize the display of the front page for users

The 3 views (personal, group, global) are not usable.

Pls add the ability to filter / add columns

The plugin Mail Analyzer should be included into the core of GLPI, because should be a normal behavior configuration.

Stevenes Donato develop this plugin:

https://sourceforge.net/projects/glpimobile/

The datacenter / rack view of 9.3 is really great, but I would suggest some enhancements regarding the power and PDU management:
For what I experience, the relation is as following:

Wall Power Outlet(s) <---> PDU Inlet(s) | PDU Outlet(s) <---> PSU Inlets (Power Supply Inlet(s) of Computers/Monitors/Network Devices, etc.

Currently there seems to be no connection between the Rack PDUs and Equipment PSU possible.

So here my ideas:

Create types Inlets and Outles, add them to PDU/PSU types and make connections between them possible: this should be roughly equivalent to the network 'Ethernet port' type.

And some minor other issues with the current implementation:

1) Plug = Outlet? And what does the 'Number' characteristic of a PDU plug mean?

2) It is not possible to add external links to PDUs

Any way to assign a (software) license to a user instead of the computer?

Most new license models (adobe, office etc) are user based, not (only) device based. 

These is a plugin:

https://github.com/FutureProcessing/glpi-fpsoftware

but seems not maintained anymore. 

I think that functionality should be provided by the core itself.

The ability to choose who can use each solution and tasks templates.

In the knowledge base we have the ability to choose the targets which can see some items. We could put that function also on the Solution and Tasks templates. What do you think?