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 ."

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

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

Hi!

I would like to propose the addition of a feature that allows users to log in and register to the GLPI system using Azure AD B2C. This integration could significantly streamline the onboarding process for new users.

Benefits:

• Faster User Integration: By enabling Azure AD B2C integration, organizations can quickly onboard new users without the need for manual account creation. This can greatly speed up the process and reduce administrative overhead.

• Domain-Based User Validation: The system could validate new users based on the domain configured in the client’s entity. This ensures that only users from allowed domains can register and log in, enhancing security and control.

• SSO Configuration: This feature would facilitate the configuration of Single Sign-On (SSO) without the need to register an enterprise application for each client tenant. This can simplify the setup and maintenance of SSO across multiple client environments.

Why This Solution is Beneficial:

Current solutions require adding login buttons for each registered enterprise application through which users authenticate into GLPI. This means that every new user must select the button corresponding to their organization, potentially revealing the list of organizations with which we collaborate.

Integrating Azure AD B2C addresses this issue. Users can log in seamlessly using a unified method, without needing to see or select between different organizational buttons. This enhances both security and user experience by keeping organizational details concealed and simplifying the login process.

Implementing this feature would provide a more modern and efficient user management experience within GLPI, aligning with current best practices in identity management.

Marcin

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.

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

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.