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
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I saw that you created a ticket with our support related to the same question, and one of our support engineers has already answered you through that ticket, so I will share their answer here to help other community members that may have the same question.
The way Git works is to create an epoch time, which is automatically generated by each local machine to determine what time it is. Bitbucket simply reads the epoch time and translates it to what time a certain change/commit/pull request happened, so Bitbucket's UI does not control this information, this information comes from Git configuration on the local machine of the user.
With that said, the only way to control this is to check user by user and confirm if their local time and timezone are synchronized with the company standard.