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

+2

Problem with rule to assign technician group

Javier Samaniego 10 years ago updated 9 years ago 1

I have a business rule that assign a technician group by category, for add and update. The group is added but i want change it.


Also the notification to the technician group is not sending in update case and I've set the notification for update ticket as "Group in charge of the ticket".

Thanks in advance.

+1

azure devops integration

Gui Ferrari 4 weeks ago 0

Integrate so I can make Azure DevOps Tickets from GLPI

+1

Geolocalização no GLPI Agent

Guilherme Oliveira 1 month ago 0

Essa possibilidade talvez seja interessante olhando para gestão de ativos, 

Utilizar o agente para coletar informações de geolocalização (GPS se disponivel, por IP Publico ou Serviços de localização do SO) e envia-lás junto aos dados de coleta do agente, coletando a geolocalização real/aproximada do dispositivo ao sincronizar o agente, podendo monitorar o deslocamento do equipamento.

Sei que já existem campos nativos que podem receber essa informação de forma manual mas acabo pensando nisso em relação a monitoria mais ativa dos equipamentos, tendo em vista os cenários mais comuns de deslocamento com dispositivos e imagino ser algo que agrega valor ao agente com um nivél mais alto de rastreabilidade.

+1

Activate the riech text editor in in the notes tabs and in the description and comments

Núria Costa 1 month ago 0

Add tge edit options in the  note tab and in the description and comments sections in the general tab like there is in the task description. 

The possibility to add links and text format will be very helpful.

+1

Consumable section in ticket creation

jozi satler 1 month ago 0

There could be a feature which would add "Consumables" section to ticket creation and editing where user could specify what consumables were used and how much.

+1

Ajout de champs sur le formulaire de tickets

h rostaingt 1 month ago 0

bonjour
Je souhaite personnaliser l’interface GLPI afin d’ajouter un champ supplémentaire dans la description des demandes et des incidents.
Ce champ devra indiquer le nom du rédacteur du ticket, c’est-à-dire la personne qui saisit directement la demande.

Cette modification doit être déployée uniquement sur un poste précis : une borne dédiée à la création de tickets GLPI.
Ce poste est un RaspberryPi fonctionnant sous Linux et héberge une instance locale de GLPI.

L’objectif est que, sur cette borne, lors de la création d’un ticket, l’utilisateur puisse saisir son nom dans un champ distinct (ou que ce nom soit automatiquement renseigné selon la configuration). Cette information devra être visible dans la description du ticket.

Pour cela, il faudra :

Ajouter un champ personnalisé (texte libre ou liste déroulante) dans l’interface de création de tickets.

Configurer GLPI afin que ce champ n’apparaisse que sur l’instance locale installée sur le RaspberryPi, sans modifier l’interface principale utilisée ailleurs.

Intégrer ce champ dans l’affichage des tickets (demandes et incidents) pour qu’il soit clairement consultable lors du suivi.

+1

automatic closure of resolved tickets and satisfaction survey

domi31410 2 months ago 0

Hello, we use GLPI among other things for ticket management; users do not always think to validate solutions to close a ticket and thus trigger the satisfaction survey. I have therefore implemented automatic closure after a delay of 7 days in 'resolved' status, but for analysis purposes and for the company's statistics, we would like to ensure that when the automatic closure occurs, the satisfaction survey is also automatically validated at its maximum score (we assume that if there are no news, then the user is satisfied?). I suspect this must be complicated, and unfortunately, I do not have the necessary skills or knowledge for development... so I am launching the idea if you find it relevant or if others are looking for this as well :) Thank you for everything you do to make this software an efficient tool. Best regards, Dominique.

+1

Add ACTUAL markdown support in notes and knowledge base

Wilbur 4 months ago updated 3 months ago 1

I just tried the 11 beta and I saw the new tools for editing text. 
It's better than before, but being used to writing Markdown on the go, this gives me the FosWiki vibes.
- I also tried to convert Markdown to HTML but even there, code block won't follow for example.

Proxmox implemented this a couple versions ago:
Simply writing this:
## Simple markdown heading
### This is so easy and effective

- Ok now a bullet list
- Easy again

```
Code block
```
Gives this 

Image 506

It could be very nice to at least toggle a markdown mode for writing then display the "View mode" in html like GLPI does.... There's a project called Perlite that perfectly fits markdown pages to a static website :https://github.com/secure-77/Perlite


Then we could make documentation flow as we link with actual cases, hardware, tickets etc, without lifting our mouse so often....

Thank you

+1

[Feature-Request] Automate GLPI Version Updating

eLBruto 5 months ago 0

Hello! As the title states, I would like to formally request the following feature :

Add a button to the following location for users with the Super-Admin rights :
The button should be here : Administration > GLPI Version Panel > Update to latest GLPI Version.

The reason I am requesting this is to have a reduced risk of botching something up.

+1

Support Firewall inventory

hramos 5 months ago 0

The GLPI agent is capable of collecting and sending information about the active firewalls on the computer; however, GLPI does not make use of this data. It would be nice if this information were reflected in the computer asset.

Example:

Windows:

"firewalls": [
{
"profile": "DomainProfile",
"status": "on"
},
{
"profile": "PublicProfile",
"status": "on"
},
{
"profile": "StandardProfile",
"status": "on"
}
],


Linux:

"firewalls": [
{
"description": "ufw",
"status": "on"
}