Earn badges and make progress
You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.