Please check if the feature has not already been requested.
If not, please describe it

Missing SNMPv3 "Context Name" parameter
Both GLPI-Server administration
> inventory
> SNMP credentials
and glpi-netinventory script missing "Context Name" SNMP v3 parameter. Context Name is mandatory in HP printers. Snmpwalk has this parameter. Please add it in available SNMP v3 crredentials.

allow to connect aggregated ports
Ethernet ports can be connected to a device, but aggregated ports are missing the "connect to" option. This would be helpful for complete overview over the network. I want to know which switch trunk is connected to which server trunk - not only which physical interfaces.

Full Text Search
IImplements a full-text search engine that can search across all tickets and the fields they contain.

Add physical ports to computer (similar as is with monitor)
Hi,
we would like to assign physical ports to computers (as already possible with monitors). This functionality would be most useful for notebooks.
Recommended options: USB (number of), USB 3 (number of), Thunderbolt, HDMI, miniHDMI, DVI, miniDVI, D-Sub, DisplayPort, miniDisplayPort, Audio Out (jack), Audio In (jack), Security card, SIM card, SD card, PCMCIA, FireWire, Paralell, PS/2, Ethernet, CD, DVD.
Even better if this was done within computer models, as suggested also for monitors in issue 2350: https://glpi.userecho.com/communities/1/topics/2350-add-usb-hub-to-monitor-ports

Components - display number of Items
When I enter the Setup - Components menu and select some type of component (e.q. Processors), I would like to be able to add Number of Items in the columns settings.
Rationale: to know, how many of each model of component we have.

100% Approval Behaviour
We would like to suggest one option to activate the possibility to only close the ticket after 100% of the approvals, in case with more than one users responsible for the approvals.

Restrict ITIL Dropdown vissibility in Ticket Creation to specific groups
Hey folks.
Currently, the only way to restrict if an ITIL dropdown is being shown while creating a ticket, is to make use of a sub-entity.
This is rather suboptimal solution (its suboptimal for almost anything to depend on different sub/entity).
We do not wish to have the default users being able to see/choose ALL of the ITIL dropdowns, since some of them are supposed to be internal to the teams using them. But those teams may also have ITIL dropdowns that MUST be visible to anyone. If they create an entry, it will be visible only for them (since its in their sub-entity).
Which makes it absolutely terrible to manage them.

Create an email notification with the number of open/closed tickets per month
Hello currently I would like to receive an email notification on GLPI with the number of tickets that is open and the number of tickets closed on each month of the year. Having no knowledge of this subject

Assigned To field and email function improvement
It would be nice to have the Assigned To field be splitted in Assigned Group and Assigned Technician. I believe it has long been like this and it would be it as an option and/or improvement.
About the e-mail functionality, in my system the Requester and Observer receives the Answers update individually, this confuses them that they are the only one receiving the update from the technician. Wouldn't it be nice to have a one e-mail thread that already includes both requester (To) and observers (CC)?
Lastly, can the ID of ticket type Request and Incident be different? It is just plain numbers and having a naming convention would just be nice. (i.e. INC-#######, I-#######, SR-#######, R-########, etc.)

Used item history unavailable from User view
When an item is being assigned to a person, it shows up under "Used items" list in person view, but there's no entry about used items under person's historical view. On the other hand, if an asset's history is being viewed, history tab shows the history of users to whom the asset was/is assigned to.
This would enable to track what has been ever assigned to user during the user's whole GLPI lifecycle, also this would enable a lot easier tracking of assets - for example assets were assigned to someone else by mistake or by somekind of automation mistake. Currently one has to know the asset name/number first.
Customer support service by UserEcho