Hello,

I would like to propose several improvements to asset management in GLPI to optimize classification and monitoring, especially for servers.

1. Separation of “Computers” and “Servers” Assets

Currently, “Computers” and “Servers” are grouped together, which can make management more complex. It would be beneficial to introduce a native distinction between these two categories to better structure information and filtering.

2. Addition of a “Criticality” Field for Servers

To facilitate the management of critical infrastructure, a “Criticality” field should be added to server assets. This field could be customizable (e.g., low, moderate, high, critical) and usable in filters and reports.

3. Customizable Colors for Better Visibility

• Ability to assign a color to the “Criticality” field values to visually identify the most critical servers.

• An option to customize the colors of the “Status” field, allowing better differentiation of states (e.g., green for “Operational,” red for “Down,” orange for “Maintenance”).

4. Improved Operating System Management

• Automatic OS-to-Version, Kernel, and Edition Linking: When selecting an OS, it should automatically suggest only relevant versions, editions, and service packs. This would prevent errors and avoid displaying irrelevant versions. For example, selecting Windows Servershould not show ESXi versions in the dropdown list. Similarly, selecting Linux should not display Windows-specific versions.

• Additional Fields for OS End-of-Life (EOL) Tracking: Automatically populate fields with OS end-of-support dates based on an integrated database or API. This would help anticipate updates and migrations.

These enhancements would greatly improve asset readability and management, especially in large infrastructures where handling numerous servers and OS versions can be challenging without automation.

Thank you for considering this suggestion!

The kanban view is nice but it would better if who could order the items in each column of the kanban.

For example, we would like to order by priority when using the tickets.

We would like to order by latest modification date or creation date.

And we would like to keep this order when reloading the page.

Thanks

Would be cool if GPLI Agent could be directly deployed trough hub.balena.io

Hello,

The function to add a new dashboard (as seem in GLPI-Inventory plug-in and on GLPI-core itself) seems to assign the "name" in English, but on GLPI Core, it seems to assign the Dashboard name based on the current GLPI user language during install into ``glpi_dashboards_dashboards`` DB.

It would be great if GLPI could provide a way for plug-in and core classes to create translatable Dashboard names. I was able to translate a name if it's in English by adding ``$dashboard['name'] = __($dashboard['name']);`` into the foreach loop of ``getAll()`` function of ``Dashboard`` class, but it would require that the name of the Dashboard is saved in English on DB and to provide a way to ensure that the translation would be gathered by Transiflex since the translation happens on the fly instead of hardcoded, and as since the Transiflex bot doesn't extract those kind of strings, it would not detect the current Dashboard names as translatable as it is.

É possível criar mais de um quadro Kanban para o GLPI? 

I would like to have the option to set the status to pending and then select a pending reason and it's attributes from a Followup Template, like you can do when you manualy add a Followup.

This would help with automation. I can check with a rule if a ticket needs to be set to pending (it needs validaton that is outside of our control), then a Folowup is added from a template. 

crear un formulario dentro de un ticket generado que genere un pdf editable para dar solucion a un diagnostico de un equipo 

The "Global search" ist not really global yet.

It should be extended to search global as per its name. It should list all items that contain the search-text. For example i search for "ABC" and I expect to get a list of all items (assets, tickets, projects) where this text was used. It does not matter if the ticket is closed or open, the project is completed or not. I want to get ALL items as it is labeled as "Global search". I even want to get tickets included if the text was used only in a comment.

This is how a normal global search works in any other ITSM-Tool. Hope GLPI gets soon also this improvement.

Hi,

After all the recent CVE for previous GLPI versions, I'd like to update our GLPI instance used for running FusionInventory to 10.0.17. FusionInventory plugin has been discontinued since 10.0.6 if I'm right and the recommanded alternative is to switch to GlpiInventory. But checking the GlpiInventory web site, it seems to support GLPI up to 10.0.11...

Is this new plugin really maintained? What is the plan to have a version supporting the recent GLPI versions?

Thanks in advance. Best regards,

Michel

Currently the Escalade plugin use the "simple" groupe name for:

- display of group modifications

- task generation of Escalade.

There could be an option to use the "full" (*) group names instead of the "simple" ones.

Rk*: "full" group name = [/parent groups name]/group name