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

Seems to be missing

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

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.

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. 

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)

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

Disable viewing of documents by everyone. Put the option of viewing a document only by a 
specific entity, group or user.

Management -> Documents

Hi,

For a more compact view of tickets in the list, it will be good to do the sum of tasks duration.

Thx

It could be useful to add more boolean operators to the rules engine that give the possibility to make equation. ()+.! and so on...