1. Juni 2021 um 18:10 #11512AnsweredMiguel FerrazTeilnehmer
we’re getting a strange issue that doesn’t happen with all tickets, but when it does, we try to assign a ticket to a owner (and it’s registered in log) but it stays assigned to Admin (the default owner).
I’ve removed a module, the ITSMChangeManagement, and 3 of the unsigned tickets were instantly assigned to the correct owners, but this could be something that is triggered after the module uninstall (like cache cleaning) because a few hours later we got the same issue with other ticket. And we just wait for a few minutes and the ticket was correctly assigned.
We didn’t detect any issue with the database queries, just the error that I’ve previous reported that register „Need Module!“ on Apache error log but it doesn’t seem related because we get that on every access to AgentTicketZoom.
8. Juni 2021 um 10:46 #11572
Today we got the same issue and I realize it’s something related to the OTOBO cache.
After executing ./otobo.Console.pl Maint::Cache::Delete the owner was already correctly set up after refreshing the TicketZoom.
8. Juni 2021 um 11:41 #11575Best AnswerSven OesterlingVerwalter
normally when changing the owner of a ticket, the cache for this ticket is deleted automatically. It seems to me, also from your other thread, that you have some custom modifications running – it is difficult to really say anything of help without looking at possible adaptions individually. For this you could contact us via email@example.com to get our professional support. Else in any case you would have to provide more information about log entries, customizations,…
Best regards, Sven
21. Juni 2021 um 13:14 #11628
Thank you for your Reply Sven.
One thing that we notice is that the user that is assigned has the correct permissions, the thing is that in the display the owner stays the same, in the queue list also stays the same.
One other thing that we noticed is that when we refresh the page the block with the owner information doesn’t try to refresh, quite different happen in other blocks:
Could this be a problem with using Memory Cache (beside using redis) for a installation that has 3 Apache servers running beside a load balancer (haproxy) with sticky sessions?
21. Juni 2021 um 13:20 #11631
Oh, one other thing that I forgot to mention.
If we set other owner and set again to the agent we set up in first place the owner is correctly displayed.
21. Juni 2021 um 15:39 #11632
One other thing that I’ve noticed in ticket log, is that the notification is sent only to the previous owner:
Changed owner to „an—@—-.up.pt“ (11). (OwnerUpdate)
Sent „Ticket owner update notification“ notification to „np—-@–up.pt“ via „Email“. (SendAgentNotification)
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.