Currently, when viewing the ticket list, users have to open each ticket individually, which can be time-consuming when managing multiple tickets.

It would be great to have an option to open several selected tickets at once in separate browser tabs.

Proposed behavior:

1. The user selects multiple tickets in the list view.

2. The user clicks on the “Actions” button.

3. A new option appears, for example: “Open all in new tabs”.

4. Each selected ticket opens in its own browser tab.

Benefits:

• Saves time for technicians who need to consult or update multiple tickets quickly.

• Improves workflow efficiency for support teams handling large volumes of tickets.

Example use case:
A technician reviewing 10 recent tickets could select them all and open them simultaneously, instead of repeatedly right-clicking and opening each ticket manually.

Olá a todos,

Estou tentando criar uma regra no GLPI para evitar que um tíquete seja fechado se não houver nenhum artigo da Base de Conhecimento vinculado a ele , mas notei que nem o Business Rules nem o plugin Behaviors parecem incluir esse campo como uma condição ou ação.

Alguém conseguiu implementar algo semelhante (talvez usando um gatilho, um gancho ou personalização de código)?
O objetivo é garantir que os tickets só possam ser fechados após a associação de um artigo da Base de Conhecimento, garantindo a documentação adequada do conhecimento antes do encerramento.

Sugestões ou exemplos são bem-vindos. Agradecemos antecipadamente!

Depending on the resource our users are requesting via a form, they need different approvers.

It would be nice if the user could select an approver from a dropdown list of approvers when creating a ticket via forms.

Right now the only option is to list all the GLPI user objects, but I only need the ones with approval role.

A solution could be a filter/pre-selector for the user objects when creating the form, or a new approver question type, so the end-users can only select the proper users objects when creating the ticket.

Hello together,

first of all, the version 11 is the best Version of GLPI of all time.
I do really enjoy now the new service desk and the possibility to have so much configurations which I can set.

I would like if the Service Catalog would get just one small improvement.
It would be nice if its possible to set the Service Catalog Category as Option for the Help Desk.

So here a small Explenation of what I am talking about:

Administration > Entity > Helpdesk home > Home tiles configuration > Type [Form, GLPI page, External Page]... But what if you also give me the ability to add my Category to it?

I would have instandly my category based forms which I can quick access without the need to first go into service catalog and then go into the category.
I would like to display for each department their service catalog on the Helpdesk home.

Thank you!

Considering network inventory needs, when creating passive devices there is no built-in way to create sockets in bulk on those devices. The socket records should inherit the parent device’s location and name, with an auto-incremented suffix based on the number of sockets we want to add. The same behavior should be available for active devices (e.g., switches) when creating multiple ports.

According to the documentation at https://help.glpi-project.org/documentation/tabs/sockets this capability appears to be implied, but I have not found it in the GLPI 10 UI

Descrição do problema:

Ao aplicar mais de uma condição nos filtros avançados de pesquisa do GLPI, o sistema apresenta os seguintes comportamentos inesperados:

• Resultados incorretos ou vazios : Mesmo quando as condições são válidas, o GLPI retorna resultados errados ou nenhum resultado.

• Erro inesperado : Em alguns casos, ao aplicar diversas condições, o GLPI apresenta um erro inesperado ou falha na execução da consulta.

• Comportamento inconsistente : O problema ocorre de forma intermitente, dificultando a identificação da causa raiz.

when i go to Administration>Inventory>SNMP credentials
i see whole list from every entities i have.
i should see only SNMP Credentials from specific entity and for child entity probably.
It is a liitle security problem. everyone from other entities can see my SNMP Credentials.

In GLPI 11, I started to explore the integration in the core of Generic Objects and FIelds plugins, which is amazing. Some ideas to eventually improve the function:

1) If we create two new assets, let's say Asset A and Asset B, and we use Asset B as a mandatory dropdown type field for Asset B, I should not be allowed to delete any Asset B which is uset by some record in Asset A table. Is there any way to implement this kind of foreign key control?

2) Other than say a field is mandatory (not empty) or not when using Custom Fields, is it possible to implement some rules about Regular Expression the field has to meet?

3) I used to import data through thee GLPI Plugin "Data Injection". Is there any plan to make it part of the core, and so compatible with Custom Assets and fields?

I want to ask about How to restrict Requesters to send ticket to members how are in there group only in assigend to field in glpi ticketing system?

Can you add a Notice field to the warranty information of a Computer asset ? A notification mail will be sent out before the warranty expires, allowing IT staff to extend the warranty in time before it expires.  

Actually a Notice field is welcome to any asset that contains warranty information (Monitors, Printers,...)