When user attempts to change his password he is not being required to type his old password.

This is serious security issue.

Password reset from should require old one.

- assign the ticket to a member of a group (all technician member receive a notification and many time 2 techician work on a ticket that is working on by an other one already)

- A mechanism that if the ticket is not processed by a tecnician in x minutes or hours, it is re-assigned to the group (or a next tecnician).

When leaving a page, for example the ticket creation page, users should be warned about unsaved changes.

Current behaviour: While writing a ticket, a user decides to "show all locations", "show all categories", or anything else that takes him to another page. The user is not notified about unsaved changes, and once they return, the form is blank again.

Expected Behaviour: When the Ticket form is not empty, GLPI should ask if the user wishes to continue and lose any unsubmitted details.

Hi,
Is it possible to have an export of all reservation?

You can create text templates for tasks, solution and follow ups, but its not possible to create a text template to validations.

Hi there,

In our company we have set up a knowledge base to write our procedures, operating methods, etc. The new interface of the knowledge base interests us a lot and we are thinking about migrating to it.

In the operation of a procedure, we must link several operating modes attached to it. However, currently it does not seem possible to link (via associated elements) two knowledge base articles together.

It could be interesting to add this possibility.

Cordially,

Dear,

I think it would be a nice feature to be able to prevent LDAP from overwriting settings that the user themselves have changed.
For example:
- User Language is set by LDAP's preferredlanguage tag. If the user changes their User Language then these changes get overwritten the next time GLPI syncs with LDAP.
- User has changed their e-mail address to that of a shared mailbox they are using so that everybody can see when they get an update on a ticket. But with a sync, these changes will be reverted.

Maybe a possibility to state that certain fields can only be overwritten during creation of the account, or always, or never. (last one might be a bit silly, but there might be some rare cases I guess).

I notice that the official manual, nor youtube, nor anything else on the internet gives a CLEAR instruction how to do a network inventory by scanning the network, adding windows pc's, servers, with or without agent, giving a complete overview of all devices using different ways. This is realy a core functionality and a great puzzle to figure out. Although the manual states some technical features commands etc, it isn't clear about how to do the steps to configure GLPI to do this properly. It is driving me nuts and it is very sad that i can't find a good manual that is clea on this matter.... Please make some, or good instruction movies (ENGLISH screesnhots and instructions) and manuals.

In long running GLPI instances rubbish increases, especially within software versions. Software is getting updated permanently and the fact is, that a lot of software versions with 0 installations stay within the database. It would be nice to have the possibility to cleanup software versions with 0 installations either by a regular cleanup task or the manual possibility to do this cleanup.

I know there are older request about this but I believe it's time to bring the idea up again. It would be great if there were an option to link phones with lines.