Tracking the history of an object in a ticket


It would be useful to have such functionality to track the circulation history (added manually) in a ticket.
Example :
I have created an object which is completed by the requester which is responsible for the time how fast the user wants his request to be resolved.
During the life of the request, this object may change.
For example, the customer reports that he wants the task to be solved in 24 hours, but the agent changes this value to 72 hours.
In general, it would be awesome if you could set yourself what should be tracked in the history (e.g. priority).

Translated with DeepL Translate: The world's most accurate translator (free version)

No offense but you may wanna have a look into the ticket history. What you’re asking for is a native core function.

1 Like