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,

Currently, for associate items to a ticket, we can only do it one by one and we must click on add button for each one.

It will be awesome to add multiple items at once, and have a temporary field to list all items to add and click only one time to the add button.

Like this ?

https://www.npmjs.com/package/bootstrap-select-v4

Sorry for my english
Thx

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

By example, in Assets, we have long caption like : "Financial & Administrative Information - Date of Purchase". That will be fine to set a short customized text instead.

Thanks

When I am editing a followup or task, if I close the window while editing, the window closes and my content added is lost.

I wish I had a popup "Unsaved content : do you really want to close the window ?"

Hello,

As asked in this forum : https://forum.glpi-project.org/viewtopic.php?id=154278

I would like to be able to add the authors name in the object of my notification mails.

It seems that conditions are not interpreted if you put them in the object field :

Bien souvent dans le traitement d'un ticket, un suivi (commentaire/question) à destination du demandeur n'est suivi d'aucun effet. Le demandeur ne répondant pas, on peut penser que le suivi répond à la demande/incident initiale et que la solution EST le suivi.

Serait-il possible de rajouter une option sur le suivi afin de transformer le suivi en solution, afin d'éviter le doublon de commentaire (ou le copier-supprimer du suivi puis ajout de solution) ?

Merci

Would it be possible to allow the addition of tables in task templates? Or change the type and put an HTML format in the task templates?