The goal is to be able to easily delete styles with a single click.

I even think it would be more useful to delete the default styles and add a button to paste while retaining the styles.

It would be nice to be able to set the impact from in forms, not just urgency

It could be great if we can change the position of each task in a ticket template because some tasks needs to be done before others.

Bonjour l'équipe et la communauté,

Je souhaite proposer une amélioration concernant l'interface utilisateur de GLPI 11, spécifiquement au niveau du menu Parc (Assets).

Le constat : Actuellement, tous les types d'équipements (Ordinateurs, Moniteurs, Réseau, Imprimantes, Périphériques, etc.) sont listés au même niveau sous le menu "Parc". Avec l'ajout d'objets personnalisés, cette liste devient très longue et difficile à scanner visuellement.

La proposition : Serait-il possible d'introduire une fonctionnalité (native ou via configuration UI) permettant de créer des sous-groupes visuels ou des séparateurs dans ce menu ?

L'idée n'est pas de changer la structure de la base de données, mais uniquement l'organisation visuelle du menu.

Exemple d'organisation :

Parc

--- Infrastructure --- (Séparateur ou Sous-menu)

 Réseau

Rack

PDU

--- Postes de travail ---

Ordinateurs

Moniteurs

--- Périphériques ---

Imprimantes

Téléphones

Cela améliorerait grandement la navigation au quotidien pour les techniciens. Qu'en pensez-vous ?

Merci pour votre excellent travail sur la v11 !

Hello GLPI Team,

We were wondering if there are any plans to re-introduce file uploads on public (anonymous) forms for the GLPI 11 release.

We understand this feature was removed due to major security concerns, but it is a very valuable feature for many workflows.

Is a new, more secure implementation being considered or planned for version 11?

Thank you for your hard work!

Hello Team, 

Hoping you appreciate my Suggested Feature. 

Instead of Updating GLPI in the Backend, 

We are hoping the update will be run through the GLPI Directly. We will have an option to update the GLPI once a new version is released without Configuring the backend ( for non-technical Users ).

1. System will Check for GLPI Update

2. Once GLPI has a new Version, the System will provide a button or field for the Update
3. The System will update it self without the interaction in the Server ( For non-technical Users )

Thanks, 

Regards, 

Joseph T. 

It would be great to improve the user experience of the service catalog to add a new type of item question in the forms.

For exemple having images instead of text to allow the user to click on one to select sub section of the forms.

it will be like having images instead of text for the Radios type.

We can do this by adding a description type with images linked to sub forms but it will increase the number of forms uselessly...

exemple of what wanted below (but without the need to have the radios button):

To maintain an ITIL compatibility on change management in GLPI it qould be great to add a new field of Change type for the changes.

This type of changes are described in ITIL :

• Emergency Change
• Normal Change
• Major Change
• Standard Change

So you don't have to recreate a tree sctructure with all the subcategory in each 'change type'

I really appreciate if i would be able to duplicate an alert

You can't reuse an old alert if you have check 'yes' to can close alert, because the updated alert remain closed.

Integrate so I can make Azure DevOps Tickets from GLPI