Add the option Vote and Rate in the Knowledge Base entries for democratized or select the better option

By default, when creating a ticket by email the writer and the requester of the ticket are equals to the email sender.

It is a good idea to implement a new feature to give users the possibility to create ticket 'on behalf of':

A user X sends an email 'on behalf of' user Y means the ticket writer will be user X, but the ticket requester will user Y.

To implement this feature, one may use a special pattern in the email body:

##From: LastName, Firstname

This feature is mainly used by service desk people when they often get emails from end-users, so instead of manually creating a ticket (doing copy/paste), then they just forward the email adding a ## in front of the "From: LASTNAME, FIRSTNAME" automatically added by the web client.

We may add the pattern in a new setting so that it can be adapted to local needs.

thank you

regards,

Tomolimo

PS: I may add this to GLPI project as it has already been developed for us.

Hello,

On the tab "Personal View" or "My View" display projects where the user is added to the team and / or project manager.

Att,

Thiago Passamani

My agency has left behind POP and IMAP protocols many years ago in favor of OWA and MAPI. Most contemporary (and unfortunately non-free) Service Desks do support native Exchange protocols. It would be amazing if these could be implemented in GLPI.

We use a reduce versión of the GUI for the final user. It´s posibble that dashboard plugin (https://forge.glpi-project.org/projects/dashboard/) come for default into the core for the final user?

For example, gather every computer in a group that has Google Chrome installed. Seems to be impossible at the moment (GLPI 10.0.17).

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

Add a different smtp server per entity in order to send email notification on différents domains.

For example: A common GLPI server for two companies with differents domains

Best regards

In addition to the top view of the server room, the possibility of seeing a complete row of racks, like the simple view of a rack but with all the storage.