If we want to force the User to fill out the Ticket-Type and therefore make it mandatory, there should be an empty value preselected, the same way as it is in Category. As in default GLPI the Type is already prefilled with request or incident.

Is it possible to create additional remote types in GLPI?

The programs included in GLPI such as TeamViewer, LiteManager, Anydesk, etc. are unfortunately too few for us in the company, and we would like to have the option to add more.

Regards.

When merging tickets, I think it could be useful to have a check box that, if flagged, could stop the sending of an email to all actors in the new merged ticket.

Thanks. 

ca serait bien de faire un pont ou une liaison entre les tickets issus des tâches des projets pour que à chaque fois que le ticket soit cloturé que le pourcentage de la tâche correspondante passe à 100%

Hi all,

I think can be usefull add some fields when I see the item under task (glpi/front/ticket.form.php?id=xxx) on this view; could be usefull that user can customize this view with filed he needs (like model etc)

Could be useful also add much criteria to search the exact item to add

Kind Regards

Stefano

Please consider moving the cartridges to the location of the warehouse location. Deleting from one object and adding to another object is very difficult.

Do the move action:

Also, the history of adding and removing cartridges is not recorded in the history. An unscrupulous administrator can delete it and not track it in any way. (there is a possibility that he will be able to take the cartridges for personal purposes).
If it is possible to implement the process of notifying the Super-Admin about the action of technical personnel over cartridges.

In shared service desk structures, it is necessary, depending on the context, in which case I include mine, the issue of departments sending tickets to each other, however, the use of the group could solve this, but it makes it impossible to manage the others elements such as contracts, assets, budgets and others, in which case the entity becomes vital. Therefore, having a simpler option for the non-IT attendant becomes necessary for ticket transfer. The current transfer focuses a lot on a technical part, but GLPI is evolving beyond the IT area, so other features seem to be needed. Obviously this is an opinion, which aims to join the group and build a collective idea.

Greetings

Go to Assistance > Tickets > Template [Above Screen]

- Click on Ticket Template and modify
- Hidden Fields - I can hide some fields, but why I can't hide "Category"?? hmm...

The list of fields available to hide is retrieved with a function that has a "withtypeandcategory" option that is set to false in the context of hidden fields.
It is not clear why it is false or why type and category are linked like this. However, it has been like this for over 11 years.
I don't know how much it would affect to allow hiding both of these fields without some extensive testing.

Thank you

When synchronizing users, adding new ones, there is no possibility of limiting to the selected OU. It would be desirable to be able to set the base DN (BaseDN) from where, with the filter set, new / old users from AD / LDAP would be downloaded / updated.

As is possible with the GUI.

Hi,

add notifications with the type "Knowledge Base" to send alerts on change of an article. In option, the target of the alert could be define by the target of the article. And the notification will be activated by an option on the article (notification : yes/no).