Hello,

Imagine you have plenty of end-users with rights only on the self-service (=simplified) interface.

Imagine you have plenty of entities, and end-users have only 'post-only' rights on one of theses entities.

The need is to give the possibility to end-users to view (and depending on rights to edit) tickets for which they don't have the formal rights (different entities) when and only when they are assigned as watchers on these tickets.

Example:

Two users: U1 and U2 have respectively 'post-only' rights on entities E1 and E2. Let's create one ticket T1 in entity E1 with U1 as requester. In this case U2 cannot see (nor edit) T1. In this case T1 can't be seen by U2 (we can't even assign U2 as watcher due to entity restrict).

1) we would like to be able to assign any user (whatever entity rights he may have) as watcher.

2) we would like to permit U2 to be able to view and add followups to T1.

More:

Of course this should also be possible via groups as watchers. When users belonging to a group (assigned as watcher on T1) don't have formal entity rights.

This need can be linked to the 'carbon copy' of users at ticket creation: when a user is creating a ticket he/she may add any other user to be watchers (independently of entities).

Thank you,

Regards,

Tomolimo

Il serait pratique de colorer une tâche dans le calendrier en fonction de la priorité du ticket auquel elle est associée

I think that multi chronometer for tasks. The intension is a better control
of task. Multi tasks running at the same time. exemple Stop the task 1 e
continue the task 2.

Some times the user call e dont have ticket. I could start the chronometer
and when stop i would have the option to create a ticket.

Hi!

I would like to propose the addition of a feature that allows users to log in and register to the GLPI system using Azure AD B2C. This integration could significantly streamline the onboarding process for new users.

Benefits:

• Faster User Integration: By enabling Azure AD B2C integration, organizations can quickly onboard new users without the need for manual account creation. This can greatly speed up the process and reduce administrative overhead.

• Domain-Based User Validation: The system could validate new users based on the domain configured in the client’s entity. This ensures that only users from allowed domains can register and log in, enhancing security and control.

• SSO Configuration: This feature would facilitate the configuration of Single Sign-On (SSO) without the need to register an enterprise application for each client tenant. This can simplify the setup and maintenance of SSO across multiple client environments.

Why This Solution is Beneficial:

Current solutions require adding login buttons for each registered enterprise application through which users authenticate into GLPI. This means that every new user must select the button corresponding to their organization, potentially revealing the list of organizations with which we collaborate.

Integrating Azure AD B2C addresses this issue. Users can log in seamlessly using a unified method, without needing to see or select between different organizational buttons. This enhances both security and user experience by keeping organizational details concealed and simplifying the login process.

Implementing this feature would provide a more modern and efficient user management experience within GLPI, aligning with current best practices in identity management.

Marcin

Today in the Administration > Inventory menu, we have 2 ways of interacting with equipment through the status that would be considered a life cycle of the equipment as a whole

The first of them, the clearest, is the default status, perfect, it is applied to practically all classes of devices that have direct inventory (Agent + SNMP): Computers, Printers and Network Device

And the second way in the same menu, at the end of the page, is called "Agent cleaning", using the "Change status" action
Today this second menu works only for computers, although the default status is applied to computers, printers and network devices

My suggestion would be to include these 2 types of device: Printer + Network Device, so that this menu could change its status, just like it already happens with computers

Or that this option was created right below this same menu, allowing you to select whether or not to use these other inventories as an option.

The logic behind this is that if the computer is necessary to have a certain level of control over its life cycle automatically, because printers and network devices that already come from SNMP inventories cannot also have the same support.

Please add variables to the ticket template. Such as the time and date in the title and description field

Add more possiblity to manage contratcs :

- add users/groups in charge of contratcs

- send notifications to the groups/users in charge

- auto-create tickets when contratcs expired, Ticket assigned to groups/users in charge