Twice this week my projects flipped from UTC to local time after minor updates in both Asana and Jira — deadlines shifted without me touching anything. This keeps showing up across tools and it’s wrecking trust in schedules; anyone else dealing with this or found a way to lock timezones down?
I stopped the drift by routing all due-date edits through a single service account locked to UTC in both Jira (General configuration > Default user time zone) and Asana — my rule: ‘one bot, UTC only’. That way every integration writes ISO timestamps with a Z and users can view in whatever zone without shifting. Are your updates coming from user tokens that might be inheriting the browser timezone?
Building on @lance92m, what finally stuck for us was switching Jira Automation to run as Automation for Jira (bot) instead of the triggering user, with that bot pinned to UTC — after that, due dates quit jumping; do you have any Asana rules/zaps running under personal tokens?
We fixed this by normalizing every due date to 12:00 UTC on write in both Jira and Asana — midnight/DST hops stopped once times weren’t landing at 00:00; @lance92m are your syncs sending date-only or dates with times?