Welcome to GLPi feature request service.
Please check if the feature has not already been requested.
If not, please describe it

+2

add exist rack to data center room

DY90 5 years ago updated by Mirkk 5 years ago 1

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. 

Image 353

+2

History Lines

Megachip 5 years ago 0

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)

+2

Improve number of queries to DB

Emanuel Wasinger 5 years ago 0

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

+2

Permissions in documents by entity or group

Marcel Beraldo 5 years ago updated 5 years ago 0
Disable viewing of documents by everyone. Put the option of viewing a document only by a 
specific entity, group or user.

Management -> Documents
+2
Under review

tickets list view : sum of tasks duration

bertrand keller 5 years ago updated by Martin 3 years ago 2

Hi,

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

Image 257


Thx

+2
Under review

Improve rules engine

eric staraj 6 years ago updated by glpi 5 years ago 1

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

+2

Ability to customize header column

Bidouille 6 years ago 0

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

+2

Display a warning when closing an unsaved followup or task

markwakwak 6 years ago updated 5 years ago 1

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 ?"

+2

Conditions in notification object

markwakwak 6 years ago 0

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 :

Image 211

+2

suivi en solution

Sico31 6 years ago 0

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