Can you add an option to convert a task in a follow in the ticket tracking system ? Often another operator made this kind of mistake (write a task instead of follow) and we cannot fix it.

Hello

To avoid ticket creation on root entity it would be useful to add an option in general settings permitting to add a message during root entity ticket creation.

Example : Warning you are on root entity !

Hi,

Is it possible to add couple of fields like HOSTNAME, IP etc in the default ticket template, so that we can filter the alerts based on those fields.

for example , to schedule the deletion of an account in several weeks or even prepare for an upcoming event

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

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 ?

In my opinion the person who have to do the task should get the reminder. Please vote to get this changed or answer your suggestion. At the moment the task creator get the reminder e-Mail. (https://github.com/glpi-project/glpi/issues/695 / http://forum.glpi-project.org/viewtopic.php?pid=319060#p319060)

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,

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)