I noticed a strange behavior in assigning tasks that appears to be a bug.

In the combo box to select user or group that will perform the task appear all the technicians. And on the next button to check the availability is visible only the users that assign the ticket or users no the group that is assigned (this seems to be the correct one)

This bug been reported? Does any new version to fix it? I'm here with GLPI 9.1.4.

There could be a possibility of limiting the Read and/or Change of assets only to "Group in charge of the hardware" or "Technician in charge of the hardware".

Because often the same type of asset (such as computers / servers) can be managed by different teams, and the solution of creating different entities is bad.

The same problem occurs with other objects such as licenses, contracts, documents, etc.

Watchers should be able to add follow ups to tickets

Hi

A new feature : ability to disable all plugins at once. It should be useful when you have many plugins and you have to disable one by one when upgrading GLPI version.

It would be useful to change the color depends on the status of the task

information : orange

Done : green

To be done : yellow

Whats the best Way to handle/inventory all these network components? 

They will be detected by FusionInventory but no asset category seems to matching. 

Also FI didn't support generic objects yet, so there is now way to move them from "unmanaged devices" to a self created asset type.

Thanks a lot for all ideas and suggestions

Migrate the current GLPI application to a Progressive Web App, which allows you to run GLPI natively on different platforms (Web, iOS, Android, etc). And to take advantage of local storage, run offline, push notifications, performance, access to hardware, access to the homescreen of the device, among others.

http://blog.ionic.io/what-is-a-progressive-web-app/

https://codigofacilito.com/articulos/progressive-apps

https://developers.google.com/web/progressive-web-apps/

Add new tab on ticket for related tickets as well as works for changes and problems. By adding a button / link to create new related ticket.