Hello team,

When a ticket is closed, we cannot change the location or ITIL category of ticket because that fields become disabled/readonly=true.

Is there a way to avoid that for super admin users ?

I would like reaffect all old tickets which are incorrect or empty.

If it is impossible to changes that behaviour, what database table is concerned in please ? 

Thank you in advance !

Hi,

Being able to send a mention to an external user would be great and very practical when we work with external parties.

Some contracts are for a specific number of hours. for example. I sign a contract in which I provide 30 hours of services. It would be great if you could add this type of contract.

Regards :)

Hi,

It would be interesting to add the possibility to filter the tickets from the global kanban by categories.

Kind regards

Hello,

Since my passage under GLPI 10 with the migration of the pluggin, there is no longer the possibility of cloning a ticket with its Requester, Group, its attachments, which can be tedious to inform at each cloning.

Do you think this could be a future integrated feature? A priori we had it formerly with GLPI 9.2 and the plugin.

Regards

La version 10 de glpi permet d'ajouter des éléments de control à distance pour des ordinateurs (Teamviewer, AnyDesk...)

Ne serait il pas possible d'ajouter RDS et MSRA ? et éventuellement Putty

Aujourd'hui, pour ajouter cette fonctionnalité, il faut passer par les liens externes  https://forum.glpi-project.org/viewtopic.php?id=282281 et déployer des clés de registre.

In Older versions (9.5.7 and olders), the ticket's writer (a technician of the central helpdesk with recursive rights and positioned at the "parent" entity in our case) could select a requester in the appropriate drop-down regardless of the entity membership of the requester (all users of all entities displayed in the drop-down). When the requester had muliple authorizations, it was possible to choose the entity in a second drop-down

In version 10.0.0, in the ticket's form, the ticket's writer has to first select the entity to be able to see the user in the drop-down. It was so appreciate to be able to select a user without first have to know obligatorily the entity membership.

It seems to be a regression or is it a bug ?

Thanks for your help

Current Notice field is not enough. Most organizations need two timings:

1. Notice, which is the official delay required by the supplier to renew the contract (by example 2 months);
2. Internal Delay, which is the time required by the organization to handle and prepare the renewal (hierarchy approval, validation process, etc.) (by example 3 weeks).

Currently, we have to merge both delays into the single Notice, but doing so 1) we lost the official delay, and 2) we have to round up delays (being unable to pick days but only months).

That's why I think adding a second Notice field (which could be name Internal Notice) would help to better manage contracts.

hello, 

Allowing the cloning of reminders with the same information

On GLPI 10.0 you cannot right click and amend spelling. It would be good to integrate a dictionary of sorts.