You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Custom assets are not visible in Treeview after migrating to GLPI 11.0.7 #116
After successfully migrating from GLPI 10.x to GLPI 11.0.7 and running the core migration command for custom objects (migration:genericobject_plugin_to_core), the Custom Assets (formerly GenericObject) are no longer visible within the Treeview plugin hierarchy.
Standard native elements (computers, printers, etc.) are correctly displayed and configurable in the tree view, but the new core custom assets are completely ignored.
Relevant log output
Page URL
No response
Steps To reproduce
Have a GLPI 10.x instance with the GenericObject plugin configured and visible in Treeview.
Migrate the instance to GLPI 11.0.7.
Run the native migration script: php bin/console migration:genericobject_plugin_to_core.
Install/update the Treeview plugin to version 1.20.1.
Go to Treeview configuration or attempt to view the asset tree.
Your GLPI setup information
No response
Anything else?
Observed vs Expected Behavior
Current behavior:
Custom assets do not appear in the Treeview tree structure.
Under Setup -> Asset definitions, there is no equivalent option or checkbox like "Use Treeview plugin" for these new native core assets.
The Treeview configuration includes all standard asset types but completely omits the custom ones.
Expected behavior:
Custom assets integrated into the GLPI 11 core should be recognized by the Treeview plugin in the same way standard assets (Computers, Monitors, etc.) are, allowing them to be enabled and displayed in the hierarchy.
Additional Context
I have already tried completely uninstalling and reinstalling the Treeview plugin, but the issue persists.
Is there any temporary workaround for this, or is an update planned to support native custom assets in GLPI 11?
This issue has been closed as we only track bugs here.
You can open a topic to discuss with community about this enhancement on suggestion website.
You can also contact GLPI editor team directly if you are willing to sponsor this feature.
Activity
github-actions commentedon May 26, 2026
This issue has been closed as we only track bugs here.
You can open a topic to discuss with community about this enhancement on suggestion website.
You can also contact GLPI editor team directly if you are willing to sponsor this feature.