Please check if the feature has not already been requested.
If not, please describe it

Add a category called Storage
We would need a new category called Storage under Assets. It would be easy to maintain our NAS like Synology and NetApp.

Configurable date format separator
Can't change date format separator.
In current version of GLPI (9.3.3) it is not able to change date format to custom settings (Setup - General - Default values: Date format, or profile - Personalization - Date format). There is only selection of date format from only 3 options:
1. YYYY-MM-DD
2. DD-MM-YYYY
3. MM-DD-YYYY
Problem is especially with separator - (dash) which is not
configurable. For example in Slovak/Czech language we use . (dot) as a
separator for date and not dash:
29.11.2018
Another languages use / as separator etc.
So it would be great to have option to also change separator for date format.
Describe the solution you'd like
Please add option to change separator for date format. Or better to able to also use custom php format:
http://php.net/manual/en/function.date.php.
For example Wordpress uses 4 predefined options a you can also use your own custom which is great:
https://www.wpbeginner.com/beginners-guide/how-to-change-date-and-time-format-in-wordpress/

Gestion des Cartes SIM et association aux téléphones
Bonjour,
J'ai vu différent post concernant la gestion des cartes SIM mais je trouve ça vraiment complexe.
Pour ne pas simplement créer toutes les entrées liées aux cartes SIM dans Configuration/Composants/Carte SIM
Il n'y aurait qu'à créer une nouvelle entrée via le bouton +, et de renseigner directement code PIN1, PIN2, PUK1, PUK2, N° téléphone etc. Puis de l'associer au téléphone souhaité.
Actuellement, je ne comprend pas pourquoi il faut d'abord créer un template, pour ensuite ajouter des cartes SIM dans Éléments ?
De plus je ne vois pas non plus l'utilité de créer une "ligne" pour chaque SIM étant donné qu'un N° est directement lié à une carte SIM.

Beta release for minor builds
New major builds have multiple release candidates and beta releases in a attempt to minimise bugs before the stable build is released.
Minor builds on the other hand don't have beta releases and often introduce new bugs.
Can you release a beta release of minor builds a few weeks before the stable build is released?
Myself and other non developers in the GLPI community would be happy to setup a staging site to test compatibility and look for new bugs.

GLPI alerts of not resolved tickets
Notification about not resolved tickets from some entity will sends not to some profile/group/etc., but to the person(technician’s), who are mentioned in ticket, like an assigned to, or to entity/group administrator. And only those tickets, which already due date expired.

A new status called Reopened tickets
It would be nice if we have a new ticket status called reopened for all reopen tickets

A a new state for assets : archived
Add the possibility to archive an item.
An archive is a new state, as it is for deleted items.
The simple way is to add a is_archived field, and filter the view in the asset's search engine.

Integrate ticket survey plugin into the core
It is very disadvantageous to move to GLPI 0.90 when this plugin is activitated in a previous version and not up to date.

Add/link ticket directly to Virtual Machine (guest) under Computer (host)
Currently it is possible to add/link ticket only to computer (host) even though it's possible to list virtual machines (guests) underneath. It would be great to add/link tickets to those virtual machines (guests).
For example it could be valuable to know how many tickets/troubles are related to which particular virtual machine when looking for repeating problems, problematic VMs and similar.
Hosts could be mixed with Linux/Windows VMs and each of them could be managed be different person so assigning tickets just to host is not enough.

Auto deleted unused document
Сервис поддержки клиентов работает на платформе UserEcho