Please check if the feature has not already been requested.
If not, please describe it
mailgate : rule for assign requester entity
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)
SLA : Can link calendar for technician groups
For example, I have 2 technician groups G1 & G2 :
Send invitation in Planning
It would be useful to send invitation for appointment from glpi planning to users.
[Cartridges] Cartridge order by user
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)
[Improvement][Ticket] Convert task to follow and vice-versa
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.
add a message during root entity ticket creation.
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 !
addition of few fields in default ticket template
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.
Hidden ticket
for example , to schedule the deletion of an account in several weeks or even prepare for an upcoming event
Notification templates do not support nested if conditions
Hello,
notification template evaluation do not support nested IFs:
##IFticket.storestatus=5## ##IFticket.status=New## ... ##ENDIFticket.status## ##ELSEticket.status## ... ##ENDELSEticket.status## ##ENDIFticket.storestatus##I prepared patch which solves it. You can/must IFs number:
##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
Servicio de atención al cliente por UserEcho