Please could you change the color of approval, this green is very awful and not very visible.

#bcda1a would be better.

commonitilvalidation.class.php line 499

like ealier version

It would be usefull to have the possibility to copy a closed ticket for technician without change status manually.

Is it possible get or associate the PC that send the ticket to the ticket?

Thank you.

The URL at today is: http://myurl.com/front/funtionality.php?id=XXX or http://myurl.com/plugin/funtionality.php the idea it's change this trough htaccess for http://myrul.com/funtionality/ID I mean the URL change to this: Example the URL for projects it is:http://myurl.com/plugins/projet/front/projet.php the htaccess change just for /project/ and when you chooose a project appear form this must be changed too so: form + ID it's reduced so the final it's http://myurl.com/projet/01 or ticket case Example the ticket URL it's: http://myurl.com/front/ticket.form.php?id=000000 the htaccess change just for /ticket/ and when you chooose a ticket appear form this must be changed too so: form + ID it's reduced so the final it's http://myurl.com/Ticket/20153001

I would like in the future version to glpi a ipam

Hi everyone,

Currently, when customizing list views (e.g. in tickets or asset inventory), it's possible to define:

• a global view (shared by all users),

• a personal view (specific to the individual),and in each case, choose which columns to display.

I believe a very useful improvement would be to introduce the concept of thematic (or custom-named) views.

Why? Because depending on the context or the user profile, the required information can vary greatly.

For example, when I’m looking at the list of computers in the inventory, my needs are not always the same:

• Sometimes, I want a technical view (OS, hardware components, network info, etc.).

• Other times, I need a financial or administrative view (purchase date, warranty, cost, depreciation).

• Or perhaps a view focused on support or ticket-related data.

Being able to create and save multiple views for different use cases would greatly enhance flexibility. Users could quickly switch between views based on their current needs.

Ideally, each view could:

• Be set as personal or shared/public,

• Be assigned to specific user profiles (e.g. Technician, Manager, Self-Service user),

• Be named (e.g. “Technical View”, “Finance View”, etc.) for clarity.

I’m not sure if this has already been discussed, but such a feature would be extremely helpful for many organizations, especially those with diverse user roles accessing GLPI.

What do you think?

In the XML file returned by GLPI Agent on Android, at the very bottom, there is a field called ‘modem’ which contains, among other things, the “IMEI” field for the phone in question. It seems that this field is no longer used anywhere in GLPI. It would be useful to be able to retrieve this element so that it can be entered directly into the serial number field for ‘phone’ type items. Currently, the glpi agent field that is transferred to the telephone box is the UUID, which is already in the UUID box. This is not useful. Would it be possible to map the ‘IMEI’ element of the ‘Modem’ to the serial number of the phone device in GLPI?

Nowadays the rule engine, in case apllied to an update of a ticket, manages only values of fileds that has been just changed and not all the fields. this limit a lot the usage of the rule engine for tickets as it cannot consider fields that didn't change.