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

+26
Started

Event Management

Pablo Rodrigues 10 years ago updated by glpi 6 years ago 3
Implement a event management, like the ITIL v3 proposes.

Control of events, where various warnings come to a one incident.
https://en.wikipedia.org/wiki/Event_Management_(ITIL)
+23

IM/Chat Feature to Create/Update Tickets

M. Cecil Dietz 10 years ago updated 10 years ago 2
It would be great to have chat functionality within the ticketing system.
Users could initiate a chat session to make a new request or update an existing ticket using an IM/chat feature. When the chat session is finished an option could exist to create a ticket from the conversation or be added as a followup to an existing ticket.
+23

New rule criteria for mail receivers

Erich Iseli 9 years ago updated by Devoteam 2 months ago 30

For us it would be really helpful to be able to make sure the mails sent to our receivers e-mail address are only sent to that address (with optionally other recipients in the CC). This would ensure that if one in the CC answers to all (and thus also to the receiver's address), I can block the creation of a duplicate ticket.

Suggested criteria: number of TO-recipients

The rule would thus look like this:

Criteria

* To email header - is not - receiver@email.address

OR

* Number of To-recipients - greater than - 1

Action

* Reject email (with email response)

+22

Phone IMEI

stefano ceccherini 3 years ago updated by Curtis Conard 2 years ago 4

Hi,

Where are we supposed to enter the "IMEI" of mobile phones ? Nowadays there are two IMEIs, I think a new "IMEI" and "IMEI2" fields should be introduced.

+22

Create a new docker official image :)

Benjamin Aimard 8 years ago updated by lucasfcnunes 12 months ago 5

Je pense qu'il serait pertinent de créer une image docker pour un déploiement plus rapide de GLPI.

+22

Automatic action run days

tyrone wyatt 9 years ago 0

Automatic actions run period only allows for start time and end time.

Unfortunately we have no option to set the run days in which the automatic actions run on.

As an example we would like the ability to set the closeticket automatic action to only run Monday-Friday.


+22
Planned

Improve booking

Pascal GUINET 10 years ago updated by glpi 5 years ago 2
We miss the following functions to booking form :
1/ User should be able to ask for a reservation by a simple form. He only add to choose a type of hardware, a begining and end date and a free field for comment. Helpdesk would after that attribute a specific material and validate that it is attributed to the user.
2/ We need a global view with the free/busy materiel at a specific date.
3/ We need a option to validate that user returned the materiel and an alerte when user did not return it passed the predicted date.
+21

mass actors remove option

Sebastien 8 years ago updated by Catherine TASSAUX 7 months ago 3

Hi

In the list of all tickets not solved, we're able to mass add an actor but we're unable to mass remove an actor


i.e. : you have 10 tickets with actor named A and you want to transfer them to B. You can't mass remove A but you can mass add B.

So it would be easier to mass remove A in one action and then mass add a new one

+21

Assign all tasks for a ticket and Change category

Jérôme STIVAL 9 years ago 0

Example : Create a new ticket (Demande) like : "Commande d'un nouveau PC"

it automatically generates a task list to do (workflow) :

- Passer la commande chez le fournisseur

- Livraison de la commande

- Installation de l'os du PC

- Installation des applications de base

- Livraison du PC à l'utilisateur

This would also make standard changes (ITIL standard)

It's look like a "Catalogue de services"


+21

Add markdown support in tickets

Alvaro Martin 9 years ago updated by drosera 4 years ago 2

Markdown support enables a better communications among the interested parties for:

  • Code snippets
  • Images (screenshots)


Also it is faster than the WYSIWYG solution field.


Markdown should be supported in:

  • Ticket description
  • Ticket solution
  • Ticket followups