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

+2

Automatic assignment of the ticket to the technician when changing status "closed (not solved)" or closed (solved)

hadesmaster il y a 7 ans 0
Hello,
Would it be possible to add in glpi an option to force the assignment of an unassigned ticket to the technician who passes the solution type field to the "closed (unresolved)" or "closed (resolved)" state in order to to prevent requests for assistance from being assigned to a technician when they are closed.
Because it happens regularly that the technicians realize the closing of the request without being granted the requests.
This is to have more accurate statistics on the number of incidents resolved by support technicians.
Thank you in advance for your assistance.
Regards,
+2

Knowledge base search from follow-up tab

serge arseneau il y a 7 ans 0

Add a button to search and add from the knowledge base from the Tickets follow-ups tab and not just from the solutions tab

+2

Root cause for incident

ClemMei il y a 7 ans 0

Would it be possible as a complement for categories to apply a "root cause" when we fill the solution of the ticket?

since we often know what was the real root cause of an incident after investigation and not when we open the ticket?

Thank you


+2

Integrate GLPI with Whatsapp PHP Library

Ricardo Alexander Perez Ricard il y a 7 ans mis à jour par Johan Cwiklinski il y a 7 ans 1

Integrate GLPI with Whatsapp Library to send notifications to users...


Check this project: https://github.com/mgp25/Chat-API


Chat-API 

Interface to WhatsApp Messenger

+2

Overview Software - Show number of installations per version

vollkommenIrrelevant il y a 7 ans 0

It would be nice if the overview could display the number of installations depending on the version.


At the moment the software menu, point version must be opened for checking. And for every single program ...


For a better overview, you could show the previous number bold and the version / number in normal.


+2

UI bug - confirming changes before leaving any page.

Alan Brown il y a 7 ans 0

I'm filing this as a bug, not an idea, due to the number of times I get complaints from users.


In assets/{whatever}/{entityname} (eg, assets/printers/foo)

If you have edited any field (eg, name) in any tab (eg, printers, name) and then switch to another tab on the same entity (eg, network ports) without clicking "Save" then all changes are lost.

The problem also occurs if moving away from any page which has been modified.

GLPI should either update automatically (not recommended) or ask if the user wishes to save before continuing (recommended)


Important:

Whilst you can argue that if a user switches to another page on GLPI without saving, he deliberately did not intend to save, this argument cannot be applied to switching between tabs on the same entity (eg, when updating or creating data for a printer or computer).


It is safer to request confirmation and saves much enduser confusion/annoyance (I have been yelled at by managers because of this behaviour, they put the blame firmly on the software, not on their failing to click "save")


Even experienced users sometimes forget to click save.

+2

Automatic assignment of a sla according to a period

chguigoz il y a 7 ans 0

Hello to all.
In my company, we have time periods of intervention in working hours (8-18h) and not working hours (18h-8 a hour, weekend and holidays).
The ticket's SLA varies according to these time periods.
To implement this need in GLPI, I created two different SLA : WO (working hours) and NWO (not working hours) with each two SLT:
- > time response = 30 mn in WO and 2 hours in NWO
- > time of resolution = 2 mn in WO and 4 hours in NWO
Both SLA are based on their own calendar, one for WO and the other one for NWO.

Examples:

if a ticket is created at two o'clock am, the SLA to apply is the NWO

if the ticket is created at 11 am in the morning on worked Monday, the SLA to apply is the WO.

In GLPI, i did'nt find how  to affect automatically the good SLA according to the period of creation of the ticket. I did'nt find possibility of using the calendar in rules.
Is somebody has an advice with regard to this need?
Thank you for your help !

+2

Organize personal view

Nicolas il y a 7 ans 0

Possibility to organize / move / hide modules in personal view

+2

Automate backup by automatic actions

Thiago Passamani il y a 7 ans 0

As a suggestion you have an option to automate the GLPI backup by automatic actions.

+2

Create combo to select active entity in login

Daniel Alves il y a 7 ans 0

 Create combo to select active entity in login. After selection, in the simplified interface, the user must register called to selected entity.