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

Surbrillance des onglets sélectionnés
Bonjour,
En 0.90.1, les onglets sélectionnés de la timeline sont blancs. Ce qui est particulièrement perturbant quand on se trouve sur le premier onglet de la timeline. Exemple :
Dans cet exemple, on ne sait pas si c'est l'onglet "Réservation" ou "Administration" qui est sélectionné.
Pouvez-vous faire en sorte que la couleur de fond du dernier élément du fil d'Ariane (ici le rouge de "Réservations") soit celle de l'onglet sélectionné (ici "Réservation") quel que soit le thème ?
La demande est la même pour permettre de distinguer les onglets sélectionnés dans :
- les marque-pages (voir capture d'écran)
- les tickets (voir capture d'écran)
Merci

Cable Management Improvement
There are several limitations in GLPI 10 regarding cable & socket management:
- You cannot define sockets with both front and rear contacts (this is required by patch panels)
- Impact analysis does not consider cables (it considers connections only)
- PDU plugs cannot be connected to assets (computers, network devices, etc)
- Lines cannot be connect
So here is my proposal:
- Sockets always have front & rear ports
- Currently connections can only be established between
- Network ports
- USB devices and computers
This needs to be expanded to allow - Network ports to socket (specifying if rear or front port is used)
- Lines to network ports & sockets
- Socket to socket (this is the case of connecting patch panels with rooms)
- PDU plug to asset
- PDU plug to PDU plug (to connect a power rail to a UPS plug)
- Cables should be optional attributes of a connection (for those having numbered cables)
- Impact analysis should show socket names, port numbers, and cable names (probably when clicking the connection line)
This can be done by other tools (such as netbox), but having it integrated in GLPI would be superb.
Also reported in forum https://forum.glpi-project.org/viewtopic.php?id=292630

add feat: approval chain: sequential approval
Hello.
It would be great if you made consistent approval in the business rules for tickets.
example:
an application was created / approver #1, then if approver #1 approved, then the ticket was transferred to approver #2, etc.

Signaturepad in GLPI
Hello would it be possible to add a signature pad in jquery that can be used to confirm assignement of assets to a user ?

The ability to combine/merge items into one.
One typical problem situation is when a department in a company first manually enters equipment(computer, mice, monitors, usb devices,printers, network devices, simcards, phones, etc) from orders and then there is a record completed by an agent whether GLPI or Fusioninventory.
Everything is ok until the wrong serial number is entered in the manually entered record (or the numbers are entered from the typist's head :/).In such a case we have a problem because 2 separate items begin to function in GLPI , one entered manually with important accounting and administrative data and the history of their changes and the other entered by the agent with technical IT data.
There is no possibility in such a case to merge them into one correct record with preservation of the history of changes.
With preservation of changes also in the fields added using the fields plugin.

Field unicity across all itemtypes
The idea would be to have unicity across itemtypes.
For example, an inventory number must be unique, whatever the itemtype.
wawax posted this idea to the project repository and tagged it as an enhancement.

Internal links in the knowledge base articles
It would be very useful to be able to place links in an article in the knowledge base, that lead to another place in the same article. This would make it easier to navigate through a long article, or even to make a table of contents.

Link consumables usage to tickets
It should be possible to link consumables to a ticket (not only to users), so a technician can inform when solving a ticket the ammount of each consumable was needed to solve the issue.

Update Documentation of GLPI
It is really hard to learn how GLPI works. The business model is complicated, and all the documentation is english or french is deprecated
Customer support service by UserEcho