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

0

server software roles and permission, per-user association

Mario De Chenno hace 3 años 0

AFAIK, client/server and web application software could be modelled as Appliance in GLPI.
Other than tracking inventory and versions, we feel the need to maintain in one place the user's roles and permission to use centralised server software. That could be implemented for example:

- Associate server software (or appliances, if that is GLPI's way) to multiple user;

- define user role profiles for server applications and associate the profiles to the users.

This way we could get a view of all users enabled to a single server application, and of all server application a single user is enabled to.

Hope this feature could be useful for all.

Let me know.

Mario

0

Ticket-Rules that connect "external senders email-domain" or "email-adress" to location

Christof O hace 3 años 0

We would like to create multiple rules, that connect "location" to ticket

0

Templates/Copy option for ldap entries

Megachip hace 3 años actualizado hace 3 años 0

Would be nice if we could use templates or at least copy ldap authentication entires. Having 30+ domains on google and they do support queries over more than one :/

0

Rule to remove IP address when status is "inactive"

Javier Samaniego hace 3 años actualizado hace 3 años 0

Rule to remove IP address when status is "inactive", currently not possible with asset rules.

Maybe related with: https://glpi.userecho.com/en/communities/1/topics/1272-new-features-for-assets-and-search-bar

Thank you.

0
Iniciado

Add SCIM user provisionning

doum hace 3 años actualizado por glpi hace 2 años 1

Currently we can authenticate with modern platform using oauth plugin (should be native in core for me...) for example with Azure

but when users can open tickets without connecting to GLPI (by phone or email for example), you have to automatically import your users in GLPI. Currently you have to use LDAP, and it's not consistent with using modern auth system

so it will be perfect to be able to use SCIM (for example with Azure AD) to create users in GLPI, whether they connect to GLPI or not

0

URL application by entity

Anto023 hace 3 años 0

Add a different application url per entity in order to use html tags in notifications


For example: A common GLPI server for two companies with differents domains

Best regards

0

Booking view with Selfie-Service profile + Simplified Interface

lage thomas hace 3 años 0

Good afternoon.

Version 9.x- At the time of scheduling the name of the person who made the appointment and the time. With the new version the permission vampo does not exist for the Simplified interface anymore, it only appears for the Standard interface.

Is there a way to adjust it to how it used to be?

Simple

Image 403

Default

Image 404

0

Make column name editable

dgrenier hace 3 años actualizado por Javier Samaniego hace 3 años 1

Adding the ability to have custom names for the columns of the inventory.

Sometimes the column names are way too long have take the space for 3 or 4 regular columns because of the title.

Here's the issue :

Image 402

How it could be fixed:


Image 401

0

TICKETS NOT AUTO UPDATE, THEY're Static

Vinicius Rocha hace 3 años actualizado por Curtis Conard hace 3 años 1

The auto update from tickets list its not working and the audio from notifications is not working. Anyone can help me?


Config > General > Default values > Auto Update Tickets (Ticket list, Kanban Project)


*The tickets do not reload the page to show the tickets, just if i press f. Summing up, the function above doesn't work*

HELP!!!

0

Ability for self-service users to choose ticket entity

gyttegott hace 3 años 0

For self-service users there should be optional to be able to select what entity a new ticket should be created in (in the "simplified interface), in the same way that entity can be chosen in the "standard interface".

In that way, a user can have a single self-service role in a root entity with the benefit of being able to create and view tickets in all sub-entities without having to change entity in the upper right corner