What happened
What this says
As at Fri 9 Oct 2026Cerys reported that date filter bounds were not being respected, returning records outside the specified range. This is blocking accurate reporting. Bethan escalated to the engineering team; no fix was shown in the ticket.
Problem: Date filter is not enforcing bounds correctly, pulling records outside the specified range and impacting analysis. Handling: Bethan triaged the issue, identified a possible timezone or parser bug, and escalated to Rory for investigation. Watch: High-priority bug with no resolution shown (final comment 2025-07-17, ticket closed 2025-08-11). Bug blocks accurate reporting for multiple teams.
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