We can define unicity on some fields, but their value can still be empty.

On another hand, we may want to set some fields as mandatory; but without any unicity.

Maybe could we consider upgrading the unicity feature to a more generic "fields setup", with unicity and mantadory (at least). Such fields must be marke as required on the html side (using the "standard" * mark, and the relevant html attribute.

Improbe surveys with more questions about of services, etc.

Language by Entity - Define language by entity with more relevant is user language, second is Entity and the last is GLPI Default Language

This will be helpfull for who use GLPI with Anonymous Ticket. When tickets came from specific e-mail address the rule move to specific Entity so the e-mails notifications will be sent following the language of the entity and not from GLPI Default language.

Firstly, thank you for this amazing application.

Please add a template option for 'Problems'. It would be so helpful.

Enable the possibility to sync the dates in the diferent options with google calendar.

There is no way to specify a contract End Date to a given day. You set a Start Date and pick a number of months in Initial contract period, then the End Date is computed. But we have some contracts that doesn't matches this algorithm.

I think that implementing one of these options would enhance Contracts management:

• adding a dedicated End Date field
  • (which could be prefilled by JS according to Initial contract period, so that user experience would not change); or
• allowing to pick a Initial contract period in days instead of only in months.

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

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/

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. 

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.