What happened
What this says
As at Fri 9 Oct 2026Cerys Llewellyn reported a date filter returning records outside the chosen week, affecting activity reporting. Bethan Lister took it on and Rory Maclean investigated. Solved 7 Aug 2025.
Problem: the date filter did not respect its bounds, so searches returned records from outside the selected week, which distorted the customer's activity reporting across operators.
Handling: Bethan Lister logged it as high priority, passed it to Rory Maclean, and first responded in 142 minutes. She then confirmed the problem back to Cerys Llewellyn.
Watch: The record shows the ticket was solved on 7 Aug 2025 and closed on 11 Aug 2025, but not what changed. Some internal and customer comments are timed before the recorded creation time, so the timeline needs checking.
Details
Updated 9 Oct 26Trail
- Internal note · Bethan Lister 17 Jul 2025 09:09Cerys flagged in standup. Date filter not respecting bounds. May be timezone issue or parser bug. Rory should pick this up.
- Public reply · Cerys Llewellyn 17 Jul 2025 11:43Our team flagged this earlier. It's affecting how we report on activity across our operators. Can this be looked at urgently?
- created · Cerys Llewellyn 17 Jul 2025 16:32I'm getting incorrect results when I apply a date filter to my searches. The filter shows I'm looking for records from one week, but it's pulling records from outside that range. This is impacting our analysis. We need this fixed. Can you help?
- Public reply · Bethan Lister 17 Jul 2025 18:54Thanks for reporting this, Cerys. Just so I've got this right, the filter bounds aren't being respected and you're seeing records outside the range you specified. I've picked this up and Rory is investigating. I'll keep you updated. Thanks, Bethan
- Status change · 11 Aug 2025 23:59