Please check if the feature has not already been requested.
If not, please describe it

name for racks row
usually in server rooms of datacenter row has name, but in glpi you can set only number. Will it be changed?

Asset tag modify
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.

Search by MacAddress
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

use HTTP_CLIENT_IP over REMOTE_ADDR toolbox.php
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'];
}
}

Global search improvement
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

Permit to customize username format
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.

Allow self-service to add observer actor after ticket creation
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).

Plugin TAG: Adding multiple tags by business rules at the time time or appending new tags in sequential rules.
Currently it is not possible to add 2 or more tags in the same rule, only one tag.
And when we split in several rules (for instance 3 rules to add 3 tags) when the 3 rules are applicable to the same ticket, the ticket is updated only with the tag of the last rule, it means, it is not adding the new tags, but replacing the one tag that was added in the previous rule.
For example:
Categories:
"Correct security issues in Linux Server".
"Correct security issues in Windows Server".
The rules are set in Add/Update ticket:
- If category = "Correct security issues in Linux Server", add tag "Security".
- If category = "Correct security issues in Windows Server", add tag "Security".
- If category = "Correct security issues in Linux Server", add tag "Linux".
- If category = "Correct security issues in Windows Server", add tag "Windows".
A new issue was added with category = "Correct security issues in Linux Server", and should be set with the tags "Security" AND "Linux", but currently when executed both rules, the issue is set only with "Linux". When I remove the Linux rule, the added issue was set with "Security" rule.
It means that the rule is replacing/subscribing all tags of the ticket, instead of add a new tag and maintain the old tags previous existent.
Usually when we decide to use tags we want to use several tags in the same ticket... not only 1 tag.
Obs.: see issue https://github.com/pluginsGLPI/tag/issues/229

problem in table glpi_computers in glpi_inventory
[2025-03-21 14:34:20] glpisqllog.ERROR: DBmysql::doQuery() in /var/www/html/glpi/src/DBmysql.php line 395
*** MySQL query error:
SQL: INSERT INTO `glpi_computers` (`autoupdatesystems_id`, `last_inventory_update`, `is_deleted`, `last_boot`, `name`, `uuid`, `domains_id`, `users_id`, `computertypes_id`, `contact`, `otherserial`, `manufacturers_id`, `computermodels_id`, `serial`, `is_dynamic`, `entities_id`, `states_id`, `date_creation`, `date_mod`) VALUES ('5', '2025-03-21 14:34:20', '0', '2025-02-26 14:24:42', 'tremw', '2A1l2520', 'foja.dom', '1006', '1', 'trelgi@FlENE', 'CZCl49NDN', '239', '1', 'CZl49NDN', '1', '0', '0', '2025-03-21 14:34:20', '2025-03-21 14:34:20')
Error: Incorrect integer value: 'fega.dom' for column 'domains_id' at row 1
Backtrace :
src/DBmysql.php:1377 DBmysql->doQuery()
src/CommonDBTM.php:730 DBmysql->insert()
src/CommonDBTM.php:1356 CommonDBTM->addToDB()
src/Inventory/Asset/MainAsset.php:711 CommonDBTM->add()
src/RuleImportAsset.php:997 Glpi\Inventory\Asset\MainAsset->rulepassed()
src/Rule.php:1537 RuleImportAsset->executeActions()
src/RuleCollection.php:1660 Rule->process()
src/Inventory/Asset/MainAsset.php:581 RuleCollection->processAllRules()
src/Inventory/Inventory.php:727 Glpi\Inventory\Asset\MainAsset->handle()
src/Inventory/Inventory.php:358 Glpi\Inventory\Inventory->handleItem()
src/Inventory/Request.php:381 Glpi\Inventory\Inventory->doInventory()
src/Inventory/Request.php:90 Glpi\Inventory\Request->inventory()
src/Agent/Communication/AbstractRequest.php:359 Glpi\Inventory\Request->handleAction()
src/Agent/Communication/AbstractRequest.php:271 Glpi\Agent\Communication\AbstractRequest->handleJSONRequest()
front/inventory.php:100 Glpi\Agent\Communication\AbstractRequest->handleRequest()
index.php:93 include_once()
Сервис поддержки клиентов работает на платформе UserEcho