[Matteo Alessio Belcore]

Otobo 11.07 linux 22 apache2

Hello Otobo Community,

I would like to request a feature that would allow operators to reset the owner of their own ticket when needed—for example, if an operator mistakenly takes charge of a ticket. At the same time, I want to preserve the existing behavior where the owner information is retained after unlocking. This is important for maintaining a record of who managed the ticket after it was closed.

Does anyone have suggestions or a possible implementation approach to achieve this? I’m interested in any ideas, code snippets, or configuration tips that could help integrate this functionality within our current Otobo setup.

Thank you in advance for your support and insights!

Best regards,Matteo Alessio Belcore

• Dieses Thema wurde geändert vor 22 Stunden, 43 Minuten von Matteo Alessio Belcore.

[Matteo Alessio Belcore]

Currently, we’re using a queue movement as a workaround to reset the ticket owner. However, we’d like to implement a function that resets the owner using a command. Initially, I considered creating a dynamic field that, when selected, would trigger the owner reset in a manner similar to the ticket queue change process. The problem is that the attribute used to trigger the reset would remain flagged once activated, so we’re looking for an alternative solution.

Any suggestions or ideas would be greatly appreciated!

Best regards,
Matteo Alessio Belcore

[Autor]

Beiträge