See http://forum.glpi-project.org/viewtopic.php?pid=315604

The background colour for all these actions is currently the same. It is hard to see "at a glance" what the status is on a long list of plugins. (Especially "enable" vs "disable")

Differentiating by colour makes it much easier to see status.

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.

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.

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.

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

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

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

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)