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

+1
Declined

DO NOT clear fields when a mandatory field is missing

Matthias Delamare 9 years ago updated by glpi 8 years ago 4

When you try to close a ticket and you missed to fill a mandatory field (eg category), the response field you took time to fill is TOTALLY EMPTY after clicking on save...

+1

add ipam fonctions

Quette Nicolas 9 years ago 0

I would like in the future version to glpi a ipam

0

[Feature-Request] Automate GLPI Version Updating

eLBruto 4 days ago 0

Hello! As the title states, I would like to formally request the following feature :

Add a button to the following location for users with the Super-Admin rights :
The button should be here : Administration > GLPI Version Panel > Update to latest GLPI Version.

The reason I am requesting this is to have a reduced risk of botching something up.

0

Asset tag modify

yair 1 week ago 0

I'm having issues trying to modify tags on assets I get from the GLPI agent.

Some agents didn't report any tag or, for example, there are some mispelled ones, and I would like to modify them.

is there any way to do it?

Thanks.

0

Support Firewall inventory

hramos 1 week ago 0

The GLPI agent is capable of collecting and sending information about the active firewalls on the computer; however, GLPI does not make use of this data. It would be nice if this information were reflected in the computer asset.

Example:

Windows:

"firewalls": [
{
"profile": "DomainProfile",
"status": "on"
},
{
"profile": "PublicProfile",
"status": "on"
},
{
"profile": "StandardProfile",
"status": "on"
}
],


Linux:

"firewalls": [
{
"description": "ufw",
"status": "on"
}

0

Search by MacAddress

Michele 2 weeks ago 0

Hello everyone,

I would like to propose a possible feature implementation for GLPI's search function. Currently, I'm using GLPI to manage my network inventory, which includes several switches discovered and inventoried via GLPI agents. These switches provide detailed information about connected devices, including their MacAddresses.

It would be extremely useful to extend GLPI's search functionality to include MacAddresses, both those of assets in the main inventory and those of devices connected to switches. This would allow for:

- Quickly locating a device: by simply entering its MacAddress in the search bar.
- Tracking devices on the network: even when they are not present in the main inventory.
- Simplifying troubleshooting activities: by quickly identifying the physical location of a device based on its MacAddress.

Does anyone know if there is a plugin, or an existing search filter that can be used to search for a MacAddress within Glpi?

I hope this proposal will be taken into consideration. 



Best regards,
Michele

0

use HTTP_CLIENT_IP over REMOTE_ADDR toolbox.php

eduardotv 2 weeks ago 0

in toolbox.php


public static function getRemoteIpAddress()

{

if (!empty($_SERVER['HTTP_X_FORWARDED_FOR'])) {

$ipList = explode(',', $_SERVER['HTTP_X_FORWARDED_FOR']);

return trim($ipList[0]); // Pega o primeiro IP da lista

} elseif (!empty($_SERVER['HTTP_CLIENT_IP'])) {

return $_SERVER['HTTP_CLIENT_IP'];

} else {

return $_SERVER['REMOTE_ADDR'];

}

}

0

Global search improvement

Martina Luna 3 weeks ago 0

It occurred to me to be able to filter the modules returned by the global search.

For example, when we search for a ticket in the global search, it returns data from other modules, related to the keyword we mainly use.

Thanks

Regards

0

Permit to customize username format

Mlx 3 weeks ago updated 3 weeks ago 0

Actually we're using Surname, Firstname in GLPI, the only other option is to use Fistname, Surname.

In my case I would like to choose Surname, Firstname, Administrative Number.

We have several users who had same Firstname and Lastname. In Active Directory it's not a problem but in GLPI, there are a lot of tickets which has not been assigned to correct person.

0

Allow self-service to add observer actor after ticket creation

Stephen 3 weeks ago 0

Self-service users should be allowed to add an observer actor after their ticket creation.

They may want to add another user in the loop for information or additionnal input from that new observer (if the permission to add a followup as an observer is allowed).