There are several limitations in GLPI 10 regarding cable & socket management:

1. You cannot define sockets with both front and rear contacts (this is required by patch panels)
2. Impact analysis does not consider cables (it considers connections only)
3. PDU plugs cannot be connected to assets (computers, network devices, etc)
4. Lines cannot be connect

So here is my proposal:

1. Sockets always have front & rear ports
2. Currently connections can only be established between
   • Network ports
   • USB devices and computers
     This needs to be expanded to allow
   • Network ports to socket (specifying if rear or front port is used)
   • Lines to network ports & sockets
   • Socket to socket (this is the case of connecting patch panels with rooms)
   • PDU plug to asset
   • PDU plug to PDU plug (to connect a power rail to a UPS plug)
3. Cables should be optional attributes of a connection (for those having numbered cables)
4. Impact analysis should show socket names, port numbers, and cable names (probably when clicking the connection line)

This can be done by other tools (such as netbox), but having it integrated in GLPI would be superb.

Also reported in forum https://forum.glpi-project.org/viewtopic.php?id=292630

I think it is valuable to have the status "cancelled" for tickets declined by requester.

Changing the status to "cancelled" is important so that the system does not include the ticket in statistics and to prevent it from being marked as a breach of an SLA.

In GLPI we have the posibility to mark follow-ups and task as a private items but there is no option mark as private the validation request and the validation response.

It could be very useful if we don't want the user see all the validations.

Like follow-ups and tasks, it would be a capability in the profile setup.

Would it be possible to add a condition for questions which allowed the selection of a specific profile, so that for example: if that profile were to be active with the user you could show/hide a question/form section based on it being active?

GLPI 10 have the reservation function native, but very simple and is not possible to costum them.
I would like to suggest some improvements to add more potential to this function.

1º option to require reservation approval (Anyone can make a reservation at the moment, without it being validated.)

2º Create the option to limit reservation time (Corrent the user can reserve a item forever) add option like 1 day, 7 days, 2 weeks, etc.

3º Add a field with terms and conditions for equipment reservations, which must be accepted by the applicant at the time of reservation.

Thanks and my best regards

Right now you cannot add notes for racks, PDUs, Passive Devices or Cables. Not sure why these are excluded but notes should be available for everything.

Currently, when editing a ticket (or a 'problem' or a 'change') and you want to attach a document, it is only possible to upload NEW documents. It should really be possible to search for an existing document, already known in GLPI database, to attach it to our ticket.

on github project wazhu, they can upgrade the agent via dashboard.

It should be very easy to implement such function in GLPI, as manually upgrade agent is pain for system admin.

procedure:

0. when there is a new agent, alert the admin in the dashboard, admin will click and download a copy to local server.

1, in GLPI dashboard, select one or multiple endpoint.

2. on the top left, ACTION button , add a "Upgrade Agent" option.

3. in the backend, mark the agent_id that need to do agent upgrade.

4. when agent check in every day, and found this need to upgrade flag on the server which associate with the current agent id, then auto download the related agent exe / pkg from server (some agent might not able to access internet due to IT policy, but able to access local GLPI server)

5. after the download, the agent will do a self upgrade.

6. after the upgrade, the agent will do a self inventory, so that the server knows the agent has been upgraded.

7. done.

Thank you.

Hi,

A technician creates a ticket for a customer, let's assume he received information by phone.
So Requester is the customer, Author is the technician.

The ticket is closed, GLPI automatically creates an external satisfaction survey (I didn't try this with internal survey). Now both Requester and Author see the survey reminder in the Personal View at the GLPI Home page (Main dashboard).

It seems only Requester should see the survey, not Author

Now in clusters you can define the items (PC or networks) that can be part of the cluster but from the Item's card is not possible to see if it is part of a cluster. I think it is useful to have this info.as it si for certificates, domains, contracts...