Open peralta00 opened 8 months ago
Hi @peralta00, is this the same behaviour as: https://github.com/znuny/Znuny/issues/503 ?
Regards Johannes
Hi @peralta00, is this the same behaviour as: #503 ?
Regards Johannes
Hi,
No not the same, and it only happens when the system needs to gather data from queues with a large amount of tickets. Eg: +5000 open tickets
Ups, misclicked
@peralta00 We created a test system with 10+k open ticket and can't reproduce this problem. Have you ever tried to upgrade to 7.0.13?
@rkaldung yes have the system on 7.0.13, migrated from OTOBO.
Hi @peralta00 please check this comment: https://github.com/znuny/Znuny/issues/503#issuecomment-1772181329 and post your output please. thanks
saw this via discord github updates, and had a spare time to simulated this. perhaps due to sub-queue filtering as video below.
update 1: also happen to filtering Service if it is a sub-services.
update 2: also happening at Ticket Status View, ServiceView, Escalation View. Basically everywhere where queue filter / service filter is being used (contains sub-queue / sub-services).
https://github.com/znuny/Znuny/assets/62957738/512c630b-183c-4465-9f64-c52779d06a8d
@mo-azfar looks like that's the problem.
I've found another bug regarding the queue filters i'll open a new issue and reference this one. (maybe its related)
Hi @peralta00 please check this comment: #503 (comment) and post your output please. thanks
Hi, Upon disabled Loader::Enabled::JS, result still same as 1st post.
attached is js detected from console
Remains in 7.0.14
Environment
Expected behaviour
Drop down with all queues to filter:
Actual behaviour
Infinite loading:
How to reproduce
Steps to reproduce the behavior:
Additional information
Developer tools console error:
/var/log doesn't have any errors related from what I can see.