This information (at least a primary IMEI) is indeed collected by the GLPI Agent, but not currently implemented on the GLPI server side. I would say that since it is a device identifier, the solution may be to add a new field directly in the Phone type. However, multi-SIM devices complicate this because then there are multiple and the numbers seem like they would be linked to SIM card slots rather than globally for the phone or SIM cards themselves. If it is required to link them to SIM cards depending on which slot they are in, it could be more complicated.

Newer versions of GLPI contain the item name in the browser tab name now. For tickets, the subject would be exposed publicly.

While interesting, would this not expose information to unauthenticated users unless only generic data is used?

The title would have to always be just "GLPI" and there is no generic description that would fit everyone's needs.

There is a native English (American) speaker on the GLPI development team as of 2020 and we have been fixing some of the little discrepancies in the default en_GB text in GLPI itself and plugins, translated the user documentation to English, and more.

Yes. As far as I can tell, this has existed since at least 0.85.

Partially implemented.

When creating a child location or child-entity, it will copy the geolocation data from the parent item if it exists. This doesn't affect locations or entities which are already created though.

Added in GLPI 10.0

Added in GLPI 9.5

Done for GLPI 10.0 with the Pending Reasons feature.

When adding a followup, you can set a pending reason template which will handle automatic "bumping" of the ticket and close the ticket automatically after a predetermined number of "bumps" without any response from the user.

Both points have been addressed in GLPI 10.

1. The filters are now in a popover accessible from a single button at the bottom of the ticket view

2. Another button was added next to the filters button to display all TODO tasks in a checklist type of view