Hi,

Is their any plugin to calculate the depreciation value of assets. 

Olá boa tarde a quem possa interessar

Gostaria de reportar um falha de exclusão de dados do banco do GLPI ao finalizar qualquer chamado, Entretanto primeiramente gostaria esclarecer que trabalhamos com plugins (Fields entre outros) afim de customizar conforme demanda da empresa, toda via ainda não sabemos se é a falha do plugin Fields ou do próprio GLPI, o que ocorre e que nos campos customizamos de inclusão de dados para adaptação ao nosso plano de negócio, afim de trazer um relatório mais preciso e personalizado dentro da necessidade dos diretores, toda via observamos que alguns dados sumiram do relatório final... e ao verificar podemos identificar que os chamado que eram fechados tanto por forma automática ou manual excluem os dados dos campos customizados pelo plugin Fields todos os dados com exceção dos numerais, e gostaríamos de saber se há conhecimento deste BUG, e caso já conhecem se há alguma forma de correção deste, caso contrário gostaria de ver a possibilidade de ajuste ou que nos ajude a identificar se é no código ou no plugins, para que possamos reportar ao comunidade para que possam ajustar o mais breve possível. Caso não tenho sido claro me coloco a disposição de exemplificar na prática o erro seja por forma remota ou de outra maneira,

Ciente da dificuldade aguardamos um retorno seja de ajuda ou de solução e nos colocamos a disposição para ajudar a acrescentar algo de nosso alcance

Sem mais atenciosamente.

Hello Guys,

I recently posted an issue and then a suggestion to glpi  issue page on GitHub (that I resolved by my own)

Based on my previous [issue](https://github.com/glpi-project/glpi/issues/16823)

I found the "problem" but as I can't make a PR, I propose these differents solution to helps the next adminsys (and avoid him to create another issue) that will try to configure LDAPS and thinking everything is correctly configured but no.

• Not working LDAPS configuration

• Working LDAPS configuration

Why do we have to specify the protocol `ldaps://` in the `server` field when we are already setting `port` field with `636`.

Then why we don't need to specify `ldap://` when it is by default the port 389.

**I propose different fixes:**

1. Add a condition in the code that checks if the user configures port 636 but did not write ldaps:// in the server field, then a detailed error log informs the user.

1. Or Change the field description Server to something like this

1. 
   Or edit LDAP configuration interface:

- replace the port field with an LDAP / LDAPS selection button

- (depending on the choice, it will pre-fill the server field with `ldaps://` and port `636` or the default ldap and 389)

My suggestions are minimum impact and here to just improve the understanding of the admins enabling LDAPS.

For example, instead of assigning 't' to ticket, assign _x('MenuShorcut', 't'), which would allow you to choose a different shortcut for each language.

In our business it is normal to sell a contract for X number of support hours. For Example, we have 40hours/month. Please add this type of contract

Hello,

I already opened tickets in the past for this issue, it has been partially solved by adding more rules to glpi inventory when filtering serial numbers.

The issue is that we cannot detect all of them and there is no way to detect bogus peripheral in GLPI itself.

One workaround is to manually set inventory management to global when we find a peripheral with a fake serial number (most of them are cheap chinese adapter or usb composite devices) but it requires an admin to find one of them.

In one year we generated more than 25,000,000 log records.
To prevent database from exploding we enabled the cron task that flush logs after one month, but we also flush valuable informations such as owner history on legit devices.

Is it possible to have a task to automatically configure management type from unit to global for example if it changes more than x times the owner in the last x days ?

Cause those lines are created over and over.
We have 500 computers which only inventory themselves once a day, if we shorten the delay, it bloats the database even more cause those devices jump after each inventory from one computer to another

Pot ser molt útil afegir un camp de correu electrònic a les dades de definició del grup.

Alguns usuaris ens demanen que enviem les notificacions a un correu electrònic del departament general quan es creen, s'actualitzen o es tanquen algunes entrades. En general, creem grups per departament.
Per exemple, si tenim un grup anomenat "Sistemes i infraestructures" (per al departament d'informàtica de sistemes) i aquest grup té un correu electrònic general com "systems.infraestructure@domain.cat" pot ser molt útil enviar algunes notificacions directament a aquest. correu electrònic.

Aleshores, s'hauria de necessitar un nou destinatari a la definició de notificació. Podria ser, per exemple, "Grup responsable del tiquet - Correu electrònic general".

I suggest adding the option to display in cards graphically show the location of the PCs.The display in the form of cards is great and the detail of the button that indicates whether the device is on or off seems fabulous to me. But I think that an ideal complement would be to provide the application with the ability to visualize the location of the devices on a floorplan.

I share an example:

It would be interesting (and an awsome time win !) to be able to choose several values in those selectors when requesting/filtering the different lists :

allowing us, for example, to perform things like in the "requester" field : 

Thanks in advance for considering this and for further upvotes.

--------------------

Lorsque l'on requète sur les différentes listes (tickets, utilisateurs, matériels, ...) ça pourrait être intéressant de pouvoir choisir plusieurs valeurs dans les sélecteurs, pour obtenir quelque chose d'identique à la 2ème image, comme sur le champ demandeur.

Merci par avance de considérer la présente amélioration, et par avance pour tous les upvotes sur cette suggestion