Bonjour,

Sur les gabarits tickets default et utilisateur, j'ai masqué 2 champs :

observateur et lieu

quand je me connecte avec un code utilisateur, les champs ne sont pas masqués.

Je ne comprends pas pourquoi.

Bonen jorunée

Upgrading GLPI to a new version is a pain. It would be great if there was a console command to upgrade GLPI to the new version.

It is not possible add more than one Group to users through Automatic User assignment rule

After add the first group, the option GROUPS is not displayed again.

It will be very usefull to Work with Groups based on Catalog Services 

Hi! It would be interesting to add the option of transferring calls between entities in the rules, as with items. Example: Criterion = technical group Action = entity assign x In this way, calls would be automatically routed between en

Is it possible for the reporting user in the simplified view not to display the history of the request and information such as the person assigned to perform the task

Hi,

I do not know if this is a big modification or not but resizing horizontaly column witdth on assistance view would rock(and thank you for already adding the column reorder in glpi 10 !)

Kind regards,

Please add apereo/phpcas to the standard GLPI build.

As far as I can see, the licensing problem that caused the library to be removed 5 years ago currently does not exist.

https://www.apache.org/licenses/GPL-compatibility.html

composer.json:
...

"ext-zlib": "*",

"apereo/phpcas": "^1.6",

"blueimp/jquery-file-upload": "^10.32",

...

Acrescentar a transferência de tickets entre entidades de forma mais simplificada, assim como ja acontece com os ativos. Hoje ao transferir um ticket o GLPI copia categoria para outra entidade, o que nao é viavel. 

Hi,

-An option to group linked tickets together on the assistance dashboard would help organisation.

-Also having the status and title of a child/ticket ticket in the linked ticket column would also be interesting.

Currently, a computer in the trashbin continues to be updated by its inventory agent. This is especially problematic when the computer in the trashbin is a duplicate, and the other one that is not in the trashbin is therefore not updated by the inventory.

A workaround could be to put all the computers in the trashbin with a status of "Deleted", and to add a criterion "does not have the status Deleted" on all the import criterias "computer update".

Suggestion: Add an "is deleted" criteria for import rules.