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.

Markdown support enables a better communications among the interested parties for:

• Code snippets
• Images (screenshots)

Also it is faster than the WYSIWYG solution field.

Markdown should be supported in:

• Ticket description
• Ticket solution
• Ticket followups

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

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. 

Hello

It would be useful to add a picture associated with model and display it in computers / network / device / phones

A new setup / pictures / 

Add a new picture

Select model associated

I have a need that is to include servers and desktop in GLPI, but a profile dont have to access the server information.

Today in GLPI this configuration is in the same screen "computer". It will be cool if create a new tipe of asset called "servers" with the same configuration of computer.

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.