include a flag on Entities form allowing to disable (deactivate) an entity no longer used, without the need to remove / migrate all the content related to this entity.

Is it possible to add the "Owner" field in the characteristics, which is the field where the user has the equipment in stock?

Hi,

I manage some assets that sometimes need maintenance, a part repair or something similar. As the data in the infocom table / section is mainly a one-time cost element, I'd like to be able to add costs whenever needed to the item. Just like it is possible for contracts. But on every object.

That would be great!

Thanks

Hello. 

It would be interesting to introduce a easier way to link to any ressource (tickets, changes, problems, computers ...) using tags or shortcodes. 

For example :

- #2105210003 or ti2105210003 => would show a proper text link (with title) to ticket number 2105210003

- ch1234, pb12041 ... comp3456, print7896 ...

I've searched but seemed not able to find anything like this

Thanks for reading
 

That would be great to have the ability to extend 'impersonate' to other technician profiles.

Defining it by Administration > Profiles and choosing what best fits the organization on a daily-basis debugging would be good to make it quicker and more dynamically.

Thanks, guys!

The GLPI could allow adding multiple mail addresses into Supplier form.

Some suppliers can have multiple emails to contact different departments.

When creating a ticket and associating a supplier into it, a drop-down could be shown to select the corresponding mail addresses.

Actually GLPI supports only a mail address by supplier.

Add ability to select "View All" in personal settings (Default entity list).

We can choose "View All" with the entity selector but we can not define this choice as default.

Currently, if we buy 100 PCs from a supplier at once, we would receive one invoice (one set of information).

In GLPI, we add 100 computer assets, then we have to manually type out 100 "Financial Information" tabs all containing the same information.

It would be way more practical, logical, convenient and efficient to create an "invoice record" to hold all the relevant information once, and then be able to link it to all the relevant assets purchased on the given invoice.

Can we add an ability to change the default view in the Knowledge Base? Some of my articles have so many pictures added as associated elements, and I'd rather just hide that column by default for all Users and just show Subject and Category.

In the table glpi_logs, when a ticket is created, the fields in the table are filled. When a ticket is updated at the fields "title" or "description", in the table was wrote the text of old value and new value in the respective fields.

It would be wonderful if this same idea can be used for tasks, because when we update a task in the ticket, in the table it's don't saved the old value , only the ID of the task.