You are not logged in.
Time to Resolve (TTR) field changes automatically to a future date/timestamp without update by an IT agent?
We noticed that the Time to Resolve (TTR) field on a ticket automatically changes after x time to a future date/timestamp then the date/timestamp that was set by an IT agent.
If we check the historical log on that ticket then there is no indication why this change of the Time to Resolve (TTR) field on a ticket occured.
Is this behaviour familiar to someone and how can this be mitigated?
Time to Resolve (TTR) field of the impacted ticket:
Historical with no log that the Time to Resolve (TTR) has changed to a future date/timestamp:
What extra information is further needed to help us with this problem/bug?
Last edited by PZBDKP (2023-12-21 12:06:54)
Offline
Made also a github issue 16236 for this problem.
Check it out and it is by design.
Offline