Add the possibility to archive an item.

An archive is a new state, as it is for deleted items.

The simple way is to add a is_archived field, and filter the view in the asset's search engine.

Currently it is possible to add/link ticket only to computer (host) even though it's possible to list virtual machines (guests) underneath. It would be great to add/link tickets to those virtual machines (guests).

For example it could be valuable to know how many tickets/troubles are related to which particular virtual machine when looking for repeating problems, problematic VMs and similar.

Hosts could be mixed with Linux/Windows VMs and each of them could be managed be different person so assigning tickets just to host is not enough.

First of all...greate job with what you guys are doing. Keep working like that!!!

My suggestion:

Add the habilitie to notify via email about historical changes made in the inventoried actives. For example:

- Know when a memory RAM or drive or any other hardware component or software were removed from an inventoried active.

- Notify about this change

- A global view where we would be able to see these changes without enter to each actives one by one.

It would be great, if the notes which you can e.g. add to computers would support some kind of Wiki/MarkDown/Rich Text to allow to add structured text. We currently maintain extensive Wikipages for each server documenting the initial setup, changes, customizations ecc. of hardware and software. It would make sense to move this information into GLPI, however with text-only it is almost impossible to display longer text in a readable way. Having e.g. MarkDown support (including proper rendering of course :-) would enable the complete documentation workflow in GLPI

Dipatch operators don't always now people on vacation, and can assign tickets to them by mistake, a simple out of office checkbox, or even better a calendar could visually show someone that a user in on vacation (Like name in red in dropdown lists)

As I am working towards training users to build KB Articles in the improved Knowledge Base, There are some custom formatting settings I would like to see used across the board. 

It would be nice if we could create a KB Template per entity so that formatting could be the same when trained technicians create new KB Articles. 

For Example: Default KB Template

(Company Logo)

PLEASE PLACE YOUR KB HEADING HERE 

The body of this knowledge base article should be in italics. Please use this formatting.

Hi,

import and export data is an importante feature for any asset management softwares. This plugin was not ported for the 9.2.x version...

Thx

I have a need that is to include servers and desktop in GLPI, but a profile dont have to access the server information.

Today in GLPI this configuration is in the same screen "computer". It will be cool if create a new tipe of asset called "servers" with the same configuration of computer.