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

+5

Accès à l'approbation du ticket depuis le mail de notification

Florian Daviaud 10 years ago updated by CDuv 10 years ago 3

Bonjour,

Concernant les notifications, la balise ##ticket.urlapprove## pointe actuellement vers l'onglet Ticket (la page générale du ticket) et non vers l'onglet Traitement du ticket. Cela permettrait pourtant à l'utilisateur d'accéder en un clic à l'approbation ou au refus de la solution depuis le mail de notification.

Merci

+5

Integrate or maintain room management like the old plugin ROOM did

tontonrico 10 years ago updated by TGr 7 years ago 4
The ROOM plugin permitted to associate equipments to the room and offered the ability to do réservations. It is a bit different as the generic object can do.
+5
Answered

ldap group sync

Megachip 10 years ago updated by glpi 10 years ago 6
Is it possible to automatic create user groups on ldap sync (e.g. first login or resync).
+5

Improvements in project management

Luis Fernando Monteiro 10 years ago updated by Curtis Conard 2 years ago 2
  • assign persons to task of project
  • define dependencies of tasks
  • define constraints of tasks ou projects
  • Automatic increment project % finished when task % are incremented
+5
Completed

Search engine for license

Walid Nouh 10 years ago updated by glpi 10 years ago 3
Add a search page for licenses
+5

Add supplier in mass actions ticket

Dev Apps 10 years ago updated by Curtis Conard 2 years ago 11

In Assistance > Tickets, add an actor assigned to supplier in mass actions

+4

Bussines Rules For Tickets

Guille 2 months ago updated 3 weeks ago 1

Currently, in each Business Rule for Tickets, we have a unique criterion that, if met, applies the defined actions when that criterion is true.


What possibility would there be to expand the number of criteria to more than one as well as the actions associated with each of them, all within the same Business Rule for Tickets?


Example for a single rule: Assignment rule according to the ticket title

Criteria #CriteriaActions if true
Criteria 1Title Contains 'printer without toner'Category Assign Change Toner
Criteria 2Title Contains 'computer does not turn on'Category Assign Technical Support
...............
Criteria NCriteria NActions N if true

This would not only simplify the number of defined rules but also allow for grouping similar criteria and actions in a single Business Rule for Tickets.

This would allow, for example, to assign service categories to tickets generated from public forms.

+4

Assign subscription plans/packages to telephone numbers

AktivniUporabnik 10 months ago 0

Request:

  • Create a new category - subsciption plans
  • Add a field or tab in the Lines menu of a specific number to assign subscription plans.
  • Include customizable details like plan name, cost, features, and duration.
  • Enable filtering and reporting based on subscription plans.

Benefits:
Improves telecom subscription management, reporting, and resource tracking.

+4

Allow use of consumables to tickets

Jesse Techno 11 months ago 0

When using a ticket, I want to assign some consumables to it and have them be adjusted in the consumables panel.

So, if I have a printer that the team submitted a ticket for more ink, 

  1. I go into the ticket
  2. click a new "consumables" tab
  3. Add the consumables to the ticket (just like items, only with the extra "consumables" data like who it's assigned to)
  4. The inventory in consumables changes to reflect the ink that was used.

+4

Create exceptions

vitorsantiagoliveira 1 year ago 0

Today, when you have a root entity and several child entities, whenever you add any item to the child entities, it ends up being shared with all of them. However, there should be an option to create an exception. Currently, you are forced to share with al