Hey @Chr1sG. It’s been a couple months and I know you’re releasing bugs fixes every week but this issue still seems to be happening. Is it a harder bug than usual bug to fix?
No problem, just curious why fixing this bug seemed to be taking longer than others since you had mentioned there in February there was a plan to fix it. I’m not sure how you prioritize your bug backlog.
I guess my wording was misleading. There is an expectation to fix it, at some point, but it has not been highly prioritized, so is not currently assigned to anyone.
I don’t know if anyone has looked into how long it will take to fix.
In general, we prioritise based on a combination of things: how often it has been reported, how painful any workarounds are, how important the customers reporting it are (we love you all, of course), how badly we are affected ourselves, how it fits in the bigger strategic vision, which developers have the skill and time to fix it, etc.
At the moment, this bug is not high priority, mostly because we don’t have a lot of complaints and the workaround (add a day to your filter criterion) isn’t that awful.