Jira reduce one hour after April 2
Hello community!
Is anyone having trouble registering an hour after April 2nd? We've detected that when registering an hour after April 2nd, Jira subtracts an hour, and we believe this is due to the daylight saving time change. I'm from Mexico, and validating with our partner, this is not only happening in my organization's instance but specifically in all instances in Mexico.
We already have a ticket with Atlassian, but the follow-up seems to be very slow because only I have reported it. If you have the same problem, it would be very helpful if you could assign yourself to this ticket JRACLOUD-80818 so that a solution can be found a bit faster.
At the moment, our response times are being affected, and we believe it could become even more critical as the days progress because it could affect automation rules that are programmed.
If you know of any alternative to mitigate the problem other than changing each user's time zone, I would appreciate it.
1 comment
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Improve user experience across Jira with global settings
Learn how to set up and configure a Jira site, manage Jira permissions, and configure Jira apps and integrations.
Learning Path
Streamline projects across Jira with shared configurations
Build Jira work items with reusable configurations called schemes, and reduce administrative work with automation.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.