Quisiera saber cómo poder configurar las notificaciones por ticket generado mediante regla para asignar un caso creado por correo electrónico, o configurar las notificaciones que se generen de entidades diferentes

By setting up a proxy server for different tenants, adding devices in the network to the inventory with automatic discovery in the network with these proxy servers

It would be incredibly helpful if you could find components based on their Inventory/Asset Number using the Global Search.

This is such an important feature it might be the reason I move away.

Currently, we use GLPI only to receive tickets from our customers, we have approximately 30 customers of which 10 are entities, the rest are locations that are within the same entity, each month a report is passed to customers, we pay a third party to pull the information from the database and pass it to Power BI, we are looking to save cost and want to try some integration of pluguin or any other free software that we can use, the data and graphs that takes the report is.

Translated with DeepL.com (free version)

Total tickets
Tickets by type (Incident vs. Request)
Tickets by status (Open, Closed, In Process, etc.)
Average resolution time
Means of contact (Direct, WhatsApp, Email, etc.)
Ticket Category (Equipment, Applications, Mail, etc.)
Root cause of the ticket
Hours spent per technician
Distribution of tickets by resolver

Can you recommend any application with which I can do this?

The idea is to generate monthly reports with graphs for each client that includes the information shared above,

Hello, 
I encountered a small issue while creating a new ticket. If the Requester (single user) field is set as mandatory in the template, assigning a requester group instead of a single user, or vice versa, throws an exception—which is expected.

So in my opinion, to improve clarity and user experience, I suggest applying a filter to ensure:

• Requester* → Only allows and displays single users.
• Requester group* → The label updates to "Group Requester",  the input only allows and displays groups.
• Both  → The label becomes "Group Requester & Requester" ; of course, the input allows and displays groups and users.

I believe this will help prevent incorrect assignments and enhance usability.

I am looking for a solution to send a message (email to the sender) back when the collector does not process the email.

I believe it would be interesting to add an option to request removal of references on the telemetry website. Several entries show the direct access link to the tool and I believe that most of the time this was not the intention. The contact form present in the tool does not work.

Hello,

Is it possible to expand the selection list for the location? 
The comment is displayed in the mouseover, but unfortunately not the room name. 
It would be very helpful if you could also search for the room name in the search bar 
and this would then be displayed in the information.

MfG Rogal

It would be great if glpi-agent, when running Agent Monitor, would show

notifications received from glpi. For example, we have notifications

turned on in the browser and when we receive a notification about, for

example, a resolved ticket, information appears in windows

notifications.

Regards Robert

When a ticket is received from a known email address it is not automatically assigned to the entity of the user associated with that email address. I cannot imagine a scenario whereby a ticket from a user would need to be associated with a entity other than that which the users belongs to.

I can create rules to assigned the entity for tickets based on the sender's email address, and this works easily for those using a corporate domain however when a user's email address is GMAIL, or similar, then he rules need to be updated constantly as new users are added.

As the information to achieve this is already in GLPI I would like to see an option that would allow tickets received via email for known senders to be auto assigned to the correct entity.