Welcome to GLPi feature request service.
Please check if the feature has not already been requested.
If not, please describe it

+2

[Improvement][Ticket] Convert task to follow and vice-versa

Sulian 9 лет назад 0

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.

+2
Завершен

Create a glpi project and task from a template in 0.901

Nour 9 лет назад обновлен glpi 9 лет назад 2

I would like to create task and model project from a template project

Because it take long time time to create similar project with the same task.

I use the 0.901 version of glpi


+2

add a message during root entity ticket creation.

Yannick 10 лет назад 0

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 !

+2

addition of few fields in default ticket template

SJP 10 лет назад обновлен asdf 7 лет назад 1

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.

+2

Hidden ticket

Joss 10 лет назад обновлен Armin01 10 лет назад 1

it would be nice to add a feature "hidden ticket" with a due date in the ticket goes up.

it would be useful to keep clear sight of tickets being processed and will bring up the desired ticket at the appropriate time.

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

+2

Notification templates do not support nested if conditions

j novak 10 лет назад 0

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


+2
Завершен

Group members view

Vincent Legros 10 лет назад обновлен 10 лет назад 3

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

+2

Hierarchical responsible & automatic watcher

Jean-charles Preaux 10 лет назад обновлен Pierre LEBEL 10 лет назад 2

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 ?

+2

Add a tab "my tickets created" in the user settings

François Legastelois 10 лет назад обновлен Tomolimo 10 лет назад 1

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,




+2
Завершен

Asset templates should be per entity and recursives (child entity yes/no)

Tomolimo 10 лет назад обновлен glpi 10 лет назад 9

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

Сервис поддержки клиентов работает на платформе UserEcho