when creating ticket by web interface, ticket is created in the requester entity( it makes sense if only one entity)

there is no rule to assign entity for mailgate : ie :

criteria : collector is my collector

action : assign requester default entity ( or assign requester 'first' entity)

For example, I have 2 technician groups G1 & G2 :

It would be useful to send invitation for appointment from glpi planning to users.

Add a form to manage cartridges applications for end user:

• Consumables Application Validation System,
• Associated Notifications,
• Wizard user based on the available stock.

(like the "consumables" plugin)

Can you add a tab with the list of users ?

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