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

+6
Completed

Remove noAUTO=1 URL parameter from email notifications

tyrone wyatt 9 years ago updated by glpi 8 years ago 2

The noAUTO=1 URL parameter in email notifications is an obstructive feature.

Users inform us that after clicking on the GLPI email notification link, GLPI will prompt them for a username/password when they are either already signed into GLPI or GLPI uses SSO (Single Sign On).

Can we have the noAUTO=1 URL parameter from email notifications either removed, an option to disable this feature or create a different notification template tag.


+6

Highlight ticket changes in email notification

dethegeek 9 years ago 0

Assuming a reader easily remembers the history of a ticket, they may quickly find what changed if the chanes are highlighted (using italic, bold or a color, or something else)



+6

History of sent mails

Ricardo Montenegro 9 years ago updated by Walid Nouh 9 years ago 3

It was important that the ticket history, or in a new tab (always associated with the ticket ) , had the emails that were sent to each of the intervening (on add Followup, Task and others).

+6

Consumables

Márcio Machado 9 years ago updated 7 years ago 3

Hello good day
Today in GLPI the Consumables are delivered (Dar) to Users and in my case and I believe for others too, use the Consumable Register for Mouse, Keyboards and sources that is considered Consumable.
Well, it would be possible that these Consumables could connect to the computer? Why that! The user is rotating and it does not take one home keyboard, and this keyboard, mouse, etc. belongs to the computer that it was connected.
Or Consumable is not for that purpose?


Thank you and congratulations for the project.
Forgive for this English so bad.

+6

Possibility to sort tickets by fields on "Tickets" tab

nicolas quiniou-briand 9 years ago updated by emmanuel haguet 9 years ago 1

It will be nice to have possibility to sort tickets by fields on "Tickets" tab for assets elements or users. See attachment :

Image 45

+6

Automatically adding technican when solution is applied

Maciej Helt 9 years ago updated by Walid Nouh 9 years ago 1
+6

Auto - KB Proposal related to the category and type of ticket

Thibaut Cauliez 9 years ago 0

To exploit the knowledge base at best when processing a ticket, depending on its type and category , it will be a good KB list is proposed to the technician to solve the problem without going to perform research itself in the knowledge base.

If any of KB self- proposed resolution allows the ticket, that acquires a point scoring KB making it more relevant. This KB will be offered in the first position the next time a ticket of the same qualification will be open.


This feature will :

-> To save time technicians
-> From more easily create KB if none is proposed in qualifying ticket
-> Prioritize the most important KB
+6

Remind the user to answer a satisfaction survey

Leonardo Gomes 9 years ago updated 9 years ago 2

When the user approves the solution of the ticket, the message appears in the lower field must tell the user "Now click this link and answer the ticket satisfaction survey ."

+6

GLPI + AI Bot

Juan Fernando Villa Hernández 9 years ago updated by Ricardo Alexander Perez Ricard 8 years ago 2

Enable an artificial intelligence bot chat in the GLPI that take and give responses of the Knowledge Base and the information into the tickets

+6

Comparison of two assets side by side to findout duplicates

btry 9 years ago updated by François Legastelois 7 years ago 4
You may find in your inventory a device with missing data. You scratch your head because you're sure it was properly filled a few days or weeks ago.

After some searching you discover this asset may be a duplicate of an other. Added by someone despite it already exists, or imported twice by an automatic inventory tool.

To ease comparison between two assets, GLPI should display them in a single page, side by side and show differences. Three buttons would help to solve the "conflict" : merge, delete A or delete B.