Hello,

notification template evaluation do not support nested IFs:

##IFticket.storestatus=5##
  ##IFticket.status=New##
  ...
  ##ENDIFticket.status##
  ##ELSEticket.status##
  ...
  ##ENDELSEticket.status##
##ENDIFticket.storestatus##

##IF0ticket.storestatus=5##
  ##IF1ticket.status=New##
  ...
  ##ENDIF1ticket.status##
  ##ELSE1ticket.status##
  ...
  ##ENDELSE1ticket.status##
##ENDIF0ticket.storestatus##

the template is evaluated then as expected.

FOREACH/ENDFOREACH is supported too.

Is it possible to include such patch in release? I believe it is useful.

Jirka Novak

Today disabled and enables users are shown as members of a group but without any disctinction.

The idea could be to mark disabled users in a group so we can visualy see enabled/disabled users

Hello,

What do you think about the idea to add the hierarchical responsible (a glpi user) for users and automatically add it as watcher when creating ticket ?

Hi,

It would be great to have one click access to their tickets created (without having to create a bookmark).

For exemple, by having a tab "my tickets created" in settings :

http://glpi/front/preference.php

Regards,

Hello,

Currently asset templates are defined in an entity and they are not inherited by child entities. One must recreate them to be able to use them in sub-entities.

Thank you,

Regards,

Tomolimo

Add possibility to assign "default" profil and "default" entity by the rule "Authorizations assignment rules".

Currently, it is just possible to add profil to an entity.

Would be cool to have the availability to set the software category via dictionary rule (Like it is possible for Software, Version, Publisher and Entity)

Currently, we can't assign more than 1 license per server. It cause calculation issues when we apply CORE or CAL licensing

EX; SQL 4 CORES licensing can't be directly assign. I have to create a software entry manually with (4) at the end, the multiplicate my cost x4 to add it to management sheet

Bonjour,

Un compte importé dans GLPI a un chemin DN (DN de l'utilisateur), ce chemin sert pour la connexion.

Problème, si la structure de l'active directory change, le chemin DN n'est plus bon dans GLPI.
ex : si CN=alain le grand,OU=Billetterie,OU=toto,OU=Utilisateurs,DC=domaine,DC=lan devient CN=alain le grand,OU=commercial,OU=toto,OU=Utilisateurs,DC=domaine,DC=lan.

Ou alors si il y a pas exemple une migration de l'AD vers un autre domaine.

Il serait bon que dans GLPI le chemin DN soit un champ modifiable que l'administrateur peut modifier si besoin pour correction.

Sinon il faut supprimer l'utilisateur et le réimporter mais je pense que les liens vers ses anciens tickets sont perdus.

It would be great to be able to specify the size of the monitor using a rational number, such as: 21.5", 20.1", 23.6", etc.