Maybe it be more easy for end users to login using email + ticket number

Was great if you can choise what tickets need validation survey.

In actual version, the system is for %, but sometimes needs force the sent of the survey or skip it.

Ajouter un workflow au plugin formcreator qui pemettrais d'attendre la cloture d'un ou plusieur ticket cible avant l'envoi d'autre ticket à d'autre cible.

Add a workflow to the formcreator plugin that would wait for the closing of one or more target tickets before sending another ticket to another target.

Hi,

Could it be possible to use a regular computer in the update source in place of manual entry? I'd like to be able to link my WSUS to al my Wndows omputer for exemple or specficy wich of my internal repo my centos server are using.

Regards,

Hello
it would be a plus to be able to add animated videos in the knowledge base and accesible since the FAQ (for tutorials a little heavier)

Add a button to wake on lan computer directly from the list of computers

Hello,

The idea is to be able to upgrade plugins in an automatic way.

Currently, when you install a new version of a plugin, the state will be 'to upgrade', and it will wait for the admin to click on the upgrade button and then after that to click on the button enable.

Could it be possible to automate this process?

A new setting (a flag) can be added that will permit to automatically upgrade a plugin. So that, as soon as, the plugin folder is updated, then GLPI will upgrade this plugin.

I'm not speaking about auto-fetching of plugins from repository, but only about upgrade process (upgrade and enable) for an existing plugin, and with a flag to tell that we are ok for this plugin to be auto-upgraded.

Thank you,

Regards,

Tomolimo

Dear All,

It would of great help if additional tags for technician are added in notification templates.

Like mobile number email I'd etc

Currently there r tags for author phone number mobile number etc.

I have built out of GLPI, FusionInventory, CustomFields, Microsoft MDT (Deployment tool) and a home made database synchronisation tool something that is close to SCCM at very low cost.

I plan to relase it as soon as it is clean enough to be shared.

Basically, I use the data from GLPI to feed the MDT database. This enable automatic OS deployment just pressing "F12" at boot (PXE boot to MDT). Our technicians just choose the OS version, the machine name, the additional applications (MS office, OpenOffice....) in GLPI and that's it.

In order to manager hardware specificities, I rely on the computer model to set some default, model based values. This used to work fine until the lastest update (21) in FusionInventory. A lot of machines where identified with a technical code for the model rather than a commercial name. This code is what MDT relies on to identify a model (plus, several models with slightly different hardware may often the same commercial name). The output on screen is much nicer (20C600JJFR is now ThinkPad Edge E540) but MDT is broken.

Therefore my suggestion is:

- Have GLPI manage both the commercial name and the technical code for computer models.

- Add one column to the glpi_computermodels table for code. Make this column indexed unique while names can be non unique.

- Show both code and name on computer description page.

- Adapt Fusion Inventory import code to store both informations.

Indeed, there will be an issue when two different versions of FI will report a different name for the same code. I guess the rule should be:

- If code and name reported are the same and conflict with an existing model where they differ, keep the one that differs as this is probably more up to date.

- If code and name reported are different, then update table. Last to talk wins! 

GLPI has only one automatic SLA action that is SLATICKET and this action has only one TICKET RECALL notification, for a 20% ticket and a ticket due date, you will receive the same notification by email. This for the actor is not good, because he will not understand very well, because he can not use more than one notification model for SLA. The ideal is to have 2 notifications for the SLA duedateNotification and Ticket Recall notice. Because this is very important for both the client and the manager to improve the company process.

Create another notification similar to TICKET RECALL for SLA duedate