In GLPI version 9.4.3, the concept of Location looks well implemented (*) and it is used in
all the 12 types of Assets, but for some reason it is not used inside
the Entities, where you only have fields for Address, Postal code, State
and Country, so it would be very useful to include the Location concept in Entities too.
As
balucha commented some time ago, we also have our more than a 1000
customers stored as entities, and it would be extremely useful to filter
their tickets using the Location hierarchy (that can be defined as
having regions in the hierarchy).
Thank you so much for this great tool
(*) Location can be defined as a hierarchy, containing fields Name, Address, Postal code, Town, State, Country, Building number, Room number, Latitude, Longitude and Altitude.
In GLPI version 9.4.3, the concept of Location looks well implemented (*) and it is used in all the 12 types of Assets, but for some reason it is not used inside the Entities, where you only have fields for Address, Postal code, State and Country, so it would be very useful to include the Location concept in Entities too.
As balucha commented some time ago, we also have our more than a 1000 customers stored as entities, and it would be extremely useful to filter their tickets using the Location hierarchy (that can be defined as having regions in the hierarchy).
Thank you so much for this great tool
(*) Location can be defined as a hierarchy, containing fields Name, Address, Postal code, Town, State, Country, Building number, Room number, Latitude, Longitude and Altitude.