[GLPI 11] Cascading filters for asset selection fields (Location → Assets)

[Chalston36]

Hello, may I suggest a new feature?

When creating a ticket, change request, or other form that contains an asset selection field, it would be very useful to allow filtering assets based on a previously selected Location.

Current behavior:

The asset dropdown displays all available assets, which can be difficult to navigate in environments with hundreds or thousands of assets across multiple locations.

Expected behavior

1. User selects a Location.
2. The Asset field is automatically filtered.
3. Only assets assigned to the selected Location are displayed.

Example

Locations:

• Rome
• Madrid
• Amsterdam

Assets:

• PC-001 (Rome)
• PC-002 (Rome)
• NB-015 (Madrid)
• SRV-003 (Amsterdam)

If the user selects Rome, only:

• PC-001
• PC-002

should be available in the asset selection list

Benefits

• Faster ticket creation
• Easier asset selection
• Reduced risk of choosing the wrong asset
• Better usability for organizations with multiple sites and large inventories

Additional idea

This could be implemented as a generic cascading filter mechanism, allowing dropdowns to be filtered by:

• Location
• Entity
• Group
• Department
• Any related inventory field

In organizations with multiple sites and thousands of assets, the asset selection list becomes difficult to use. Filtering assets by location would significantly improve ticket creation speed and reduce selection errors.

Thank you in advance for your attention to this matter.