I have a view that is built to house newly created tasks that need to be reviewed.
I have them Grouped By: Created On.
The only issue is – it seems to be performing time travel (or maybe the “Group By” feature is using a different time zone than the Created On field)
See screenshot: I created a task just now – it has it in a group saying it was created… Tomorrow I created a task tomorrow already. I’m super on top of things, doing my work in the future
@Bryan_TeamKickstart - tested and reproduced this. I’m thinking you’re right and it’s a time zone issue (since created_at is stored as a full ISO string unlike due_date and start_date). I’m wondering if the grouping specifically is just pulling the date from the ISO string (machine time zone-agnostic) and the field is using your machine time zone to display the local date of the ISO string. No idea why that would be the case, but that seems like the simplest explanation. Do the “time traveling” tasks all get created between 8pm and midnight ET?
Depending on volume, maybe sorting by creation date instead of grouping would work? That definitely does preserve the correct order, but you obviously lose the nice visual breaks of the grouping.
Hi @Bryan_TeamKickstart and team, sorry for the delay! This definitely sounds like a timezone issue.
I haven’t seen this issue with “Group by” specifically, but I’ve seen similar cases with timezone affecting recurring tasks before. I’ve reported this to our Developers and will let you know once I have any updates