`Html::includeHeader()` offers hooks for plugins to add CSS and JavaScript assets (via `$PLUGIN_HOOKS['add_css']` and `$PLUGIN_HOOKS['add_javascript']`) but nothing for plain HTML code (static or dynamically generated).

Modifying `Html::footer()` would allow plugins to add code on/as footer.

More method are impacted because some are dedicated to the help pages, modal/pop-up, etc.

I suggest adding hooks (say `$PLUGIN_HOOKS['add_code_in_header']` and `$PLUGIN_HOOKS['add_code_in_footer']`) for the plugin to allow more customization of GLPI general interface.

In my case, I am building a plugin to add snippets of plain HTML codes (disclaimers, notes, analytic trackers, etc.) on any pages.

Bonjour,

il serait bon d'ajouter un bouton "enregistrer et fermer" pour chaque formulaire (ticket, ordinateurs, imprimantes,...). A chaque modification, on ne veut pas forcement rester sur le formulaire mais revenir au résultat de notre recherche.

Hello

It would be relevant to add a picture next to the first word of entries of knowledge base

image - word tips

Define a whitelist of IP or host that are able to use autologin function

Hello everyone

I did not see that request.

How is working the mail notification when using same recipients on differents entities ?

I.E. : if I use 2 entities named root and root2.

Recipients in Ticket Notification template are Admin and technician

Users sends mail to helpdesk and if no rule is set, so what's about the notification ? The technician will receive twice mail notification saying "New Ticket" ?

So my request would be if we could set Notification template (i.e. : for New ticket) per entity ?

Currently large RSS items are not displayed well when moused over. I suggest truncation. 0.90.5

I think an example dataset that covers every feature of GLPI (computers, network ports, patch network, softwares/licences, tickets/problems/changes, budgets, etc.) would be helpful.

My opinion is that some uses GLPI as an inventory database for their machines/licences, others for helpdesk management (with or without team planning).

And I think few uses the full potential of GLPI (partly because not everybody needs to).

When you are not aware of the problems that GLPI gives answers to, it's difficult to truly understand how some parts works and should be used.

In my case: I use inventory, helpdesk and documents. I also use GLPI to model how my network equipments are connected together. But I have no idea of what the "Project" part aims to offer: the best I can do is fill the blanks in the forms and see where it leads me...

By looking at an example dataset I might understand what each part of GLPI is supposed to do and use it as it was thought/imagined by original author.

This would also express some common "patterns" we are using (eg. "states" dropdowns).

Have the possibility to pin tasks in order to view at first sight a "task to do" for example. In the same way like pin a topic in a forum. Indeed in consistent tickets, it's difficult to find "tasks to do" among the other tasks and followups and not forget to do them.

Epingler une tâche afin de voir en premier les tâches par exemple de type "A faire". En effet dans les tickets conséquents, il peut être difficile de repérer les tâches qu'il reste à faire et à ne surtout pas oublier.

Hello

I know my request is tricky and non standard, but...

Would it be possible to open a ticket automatically with GLPI when we receive an internal call ?

Thank you for your answer

Currently the only way to configure inheritance for computers to child entities is to do it manually on each computer or to edit the MySQL database.

To set it for all newly created computers, you have to edit the MySQL database.

It would be cool to have a toggle in configuration to set it, and to be able to mass edit the computers to set it.

(see http://forum.glpi-project.org/viewtopic.php?pid=325807#p325807)