Please check if the feature has not already been requested.
If not, please describe it
Option to select if the user will or won't receive emails by default
There are some users that I don't want GLPI to receive emails.
I know there's the option to disable the follow up in each ticket. But I'd like to set it up on users by default.
For example:
The event monitoring system that opens tickets in GLPI by email doesn't need to receive updates about the ticket progress since it's not even a person.
This happens less often but there are some users that don't want and don't need to receive the emails from the Service Desk software.
Currently, I need to deactivate it every time in each ticket. However, when we receive more than 20 or 30 tickets of this kind (events monitoring system) it's inhuman to do it always.
Notification action for emails not accepted by anonymous users
When the 'Allow anonymous ticket creation (helpdesk.receiver)' is not active and a new user starts working and sends an email to the GLPI receiver, the system ignores the email but nothing is sent to the sender. So nobody knows the email was sent and ignored, besides the only person who sent it before and didn't receive an answer.
That would be of good use to have a notification action for ignored emails or even a list or something to know the ignored/blacklisted emails.
- The email comes in
- GLPI doesn't find a user match for the sender's email address
- GLPI ignores it
- GLPI sends the sender an email explaining that the message was ignored
- OR/AND
- GLPI stores a list of ignored messages and an admin could manage the destination for each message correctly
This way we could understand well what is happening on the Receiver address and no user is going to wait and get no response.
Arthur Schaefer, MBA
It is necessary to make it possible to change the type of asset.
It is necessary to make it possible to change the type of asset. For example, during inventory, network printers get into network devices and you need to transfer them to the "printers" type or server management interfaces (aka ILO) fall into network devices, but you need to transfer them to the "computers" type, or UPS with a network interface get back into network devices, but it is necessary to transfer them to the type "power distributors", or the IP phones fall into the "network devices", but it is necessary that they be of the type "phones".
ability to create link between Users and contracts (used items)
Hi, please add ability to create link between Users and contracts (used items). It will be usable to manage contracts related and used by users, for example contracts for cellphone phone numbers with telecomunication operators.
Regards Krzysztof
Network ports on monitors
I manage some TVs in the monitors section of my GLPI and some of them have wifi. So, I'm looking for a possibility to add network ports to a monitor just like it works with computers and network devices.
add exist rack to data center room
We found only creating a new item is available when insert a rack into server room. Could you please also provide a method to adding exist rack to server room. It's very convenience for user.
History Lines
It would be awesome, if the History of the Lines also shown, when e.g. a Sim-Card was attached or removed (atm this is only shown in the Sim-Card-Link)
Improve number of queries to DB
Hi.
I am using GLPI 9.4.3 and GLPI 9.4.4. I have noticed that performance has declined and I think I know why.
In a fresh installation GLPI needs 66 queries to DB to show the tickets list window (without tickets).
For do that, it need to open 3 sessions to DB.
GLPI_9_4_4_ticket_list_fresh_installation.log
When 1 ticket is load, GLPI needs 76 queries to DB to show the ticket list window (with 1 ticket).
Again, for do that, it need to open 3 sessions to DB.
GLPI_9_4_4_ticket_list_1_ticket.log
When 2 tickets are load, GLPI needs 84 queries to DB to show the ticket list window (with 2 ticket) and open 3 sessions.
This behaviour produce that when the tickets number increase, the number of queries to DB increase too.
In addition, some queries are repetead several times.
For example, the queries to load users' data are repeated for every time that the user have to be showed in the tickets list (like requester, observer or technician).
Maybe you can save user information in an array on the first search and check there every time the user must be showed more than once.
I think that is important reduce the number of queries because in a production environment, to display a list with 15 tickets, GLPI needs to make about 900 queries to the database.
glpi_mysql_without_genericobject.log
And finally, having the genericobject plugin activated with 80 types of objects approximately, GLPI needs to do almost 11200 queries to the bd to show a list with 15 tickets. In this case, some queries are repeated more than 1000 times.
glpi_mysql_with_genericobject.log
I await your comments.
Best regards.
Emanuel
Servicio de atención al cliente por UserEcho