Hello good day
Today in GLPI the Consumables are delivered (Dar) to Users and in my case and I believe for others too, use the Consumable Register for Mouse, Keyboards and sources that is considered Consumable.
Well, it would be possible that these Consumables could connect to the computer? Why that! The user is rotating and it does not take one home keyboard, and this keyboard, mouse, etc. belongs to the computer that it was connected.
Or Consumable is not for that purpose?

Thank you and congratulations for the project.
Forgive for this English so bad.

It will be nice to have possibility to sort tickets by fields on "Tickets" tab for assets elements or users. See attachment :

To exploit the knowledge base at best when processing a ticket, depending on its type and category , it will be a good KB list is proposed to the technician to solve the problem without going to perform research itself in the knowledge base.

If any of KB self- proposed resolution allows the ticket, that acquires a point scoring KB making it more relevant. This KB will be offered in the first position the next time a ticket of the same qualification will be open.

This feature will :

-> To save time technicians
-> From more easily create KB if none is proposed in qualifying ticket
-> Prioritize the most important KB

When the user approves the solution of the ticket, the message appears in the lower field must tell the user "Now click this link and answer the ticket satisfaction survey ."

Actually we have a rule to change the status to pending when an approval is sent to compliance user. But the status does not come back to process assigned.

It should be great to add a rule when the approval is granted change the status to process assigned

Enable an artificial intelligence bot chat in the GLPI that take and give responses of the Knowledge Base and the information into the tickets

When new notifications are created on a GLPI version, an upgrade to this version active these notifications.

For example, if you upgrade from 0.84 to 0.90, following notifications will be active after upgrade :

• New change
• Update change
• Resolve change
• Add task
• Update task
• Delete task
• Close change
• Delete change
• New project
• Update project
• Delete project
• Receiver Errors
• New project task
• Update project task
• Delete project task

This is the default behavior of GLPI : new notifications are active. If you don't know, our users may be surprised.

Please disable new notifications after upgrade.