When creating a new user, it's showing the "Last Name" and "First Name" fields into USA format.

In my country (Brazil), it's more common we fill the First name and the Last name after.

Into my User preferences and at Global preferences, we'd set the Display order of lastnames firstnames (Ordem de exibição de sobrenomes e nomes) to "First Name, Last Name" (Primeiro nome, Sobrenome).

It would be great if GLPI also reflect this preference at it's forms.

I am using GLPi templates to set up very specific workflows. Each ticket template has its own knowledge base article.

It would be awesome if I could set up a knowledge base article as a predefined item in a ticket template.

This would save as a lot of work and it would be as simple as being able to set a URL link when you define a template.

In a ticket, Automatically filter the list of equipment in the "element" tab in relation to the location of the ticket.

When i clon a ticket the clon is cloned in the same state. If this is closed and i have not permmision to reopen i cant use this utility. I think is more usefull to clone a ticket on new state.

Can you work on next update to make Custom fields be able to:

- Auto create tag for the field created

- Use the tag with Email notification

This way we can send emails with custom field information, this would improve a lot the usability of the plugin what is already very good, if needed some investiment let me know i will be more than happy to help.

Put the Save button and trash up there along with the options, sometimes you have called with a lot of text, you have to scroll down to the end to save

Example:

Hi,

like for follow, transform a task in a ticket and link this new ticket as a son

GLPI etant avant tout un outil destiné aux helpdesk, ceux-ci sont aussi très friands de procédures/documentation diverses et variées.

Je suis étonné que GLPI ne propose pas un tel module afin de gérer les procédures de façon efficace, propre, lisible avec recherche, visionneuse, appels a des ressources serveurs externes et autres outils de visionnage.

il y a bien certes un module documents, mais celui-ci est un joyeux b.. fourre-tout qui regroupe aussi bien la doc de l'équipe IT que les documents transmis par les utilisateurs via les pièce jointes des tickets (et obsolètes/inutiles au bout de plusieurs mois).

L'idéal serait de pouvoir publier nos documents avec metadonnées simples et classements/sous classements possibles.
Un paramétrage permettrai même de pointer vers un dossier réseau pour le dépot de ces fichiers (sinon, copie sur la base GLPI qui va grossir, grossir ...).

Pourquoi pas indiquer les lecteur/visionneuses en local selon les extensions (pdf, open office, office, etc) pour éviter tout téléchargement de fichier en local !

Ce la ressemble certes à une GED, mais plus légère, souple et implémentée dans GLPI donc facilement accessible au helpdesk et autres équipes.