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

+3

Auto close for ticket where no reponse is received fromt the requester

plcadmin 9 лет назад обновлен tyrone wyatt 9 лет назад 1

A feature that would allow the auto closing of tickets after a preset time when no response is received from the requester would enable the automatic management of tickets waiting for input.

This would be used where a question has been asked by the technician to the requester to complete an action and comment or where input on the current status has been requested. I have situations where a requester will never reply and the tickets have to be manually cleaned up on regular basis.

Companies such as Google Support use this type of feature as a standard part of the ticket handling.

+3

Ticket creation delayed

ylagva 9 лет назад обновлен tyrone wyatt 9 лет назад 2

As recurent ticket, create ticket with opening date and ticket template selection.


this feature would allow automatically open a ticket at a future date . Example : give rights to xxx at 1st february 2016.

+3

Add Associated Items Tab

Ryan Bernier 10 лет назад обновлен 10 лет назад 0

If each type of asset could have a section that showed all items it is associated with, by virtue of connections with other items. For example, I could have the following logical connections between items:


Computer-Phone-SIM-Contract


I'd like to be able to see the Contract (Phone Number), within the computer's properties. Or from the Contract's properties, see the SIM, Aircard and Computer. Bonus if it could show you the logical connections, in the case that a single computer has multiple aircards or an aircard has multiple SIMs.


Computer1-Phone1-SIM1-Contract1

Computer1-Phone1-SIM2-Contract2

Computer1-Phone2-SIM3-Contract3


Currently I have to click through each item to figure out what line of service is on the computer I am working on.

+3

Export a Incident or requirement in a Zip file

Juan Fernando Villa Hernández 9 лет назад 0

Enable the posibility of the export a incident o requirement in a Zip or Tar format with the information, task, documents, etc.

+3

Templates to fill categories, task, source etc.

Juan Fernando Villa Hernández 9 лет назад обновлен anonymous 9 лет назад 2

Templates to fill categories, task, source by industries to make more easy the setup, configuration and parametrization of the GLPI

+3
Отклонен

Record in a drop down the previous user that was assigned to a asset

SheridanUser 10 лет назад обновлен glpi 5 лет назад 2
We track a lot of user inventory and when a user leaves we clear out the user section so we know its free to be redeployed.

Adding in a previous user drop down so we can sort be previous users instead of going into each asset and viewing the history or sorting by users names in the history section would be a great time saver.
Ответ
glpi 5 лет назад

Hi,

Thanks for your suggestion.

Search filters exist in "History" tab since GLPI 9.3

Regards,

+3

Ticket creation from another entity

ylagva 10 лет назад 0

It would be usefull to add in profile, an option allowing ticket creation from another entity.



+3
Завершен

Store assets GPS location

Walid Nouh 10 лет назад обновлен glpi 7 лет назад 3

Store, for each asset, the X last GPS positions.

Display, for each asset or a group of assets the positions on a map

+3
Завершен

Better UI : Location improvement or buttons

stephane dombre 10 лет назад обновлен glpi 5 лет назад 3
If you use multiple level of location (ex : First Site > Building A > Level A1 > Room 3), the current drop-down menu is a mess.
Changing location (ex : i just want to see Building B computer) take time and a good eye to catch the right line.
Could it be improved ?
A way would be to add an optional location bar (with multiple lines : line 1 shows lvl 1 as buttons. Select a button and another line appears showing lvl2 location of the selected lvl 1 and so on...).
+3

Notifications : unique mail

nicolas quiniou-briand 9 лет назад обновлен 9 лет назад 2

When a notification contains multiple recipients, GLPI sends one mail per recipient.

Is it possible to change this behavior to send an unique mail with headers ?


For example, when recipients are requester and watcher. GLPI should send an unique mail with following headers :

- To : requester(s)'s e-mail address(es)

- Cc : watcher(s)'s e-amil address(es)

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