Summary

When visiting the License Details screen in Bitbucket Admin, you may notice that the expiry date of the license is sooner or later than your invoice suggests - or the details in your Atlassian account. The discrepancy may be a day or more.

Cause

There is a discrepancy in the timezone when the products and Atlassian license system handle a license expiry date.

The License contains an expiry date in string format like 'YYYY-MM-DD' at US Central Standard Time (UTC-6). In Bitbucket, this license expiry date is converted to UTC timestamp by complementing time with '00:00:00' as Australian Eastern Standard Time (UTC+10) and is displayed using your local time zone. You can adjust your User Profile to specify a time zone, or make the changes for all users in Bitbucket.

Your license will expire at the specified date midnight in AEST (UTC+10). All dates and times expressed in invoices, emails, and your Atlassian account will be displayed in CST (UTC-6).

If you have doubts about when your license expires, please don't hesitate to contact Atlassian Support.

To fix this, the products and Atlassian system should handle the license expiry in the consistent timezone. Please watch BSERV-11038 for update.

This discrepancy also exists in Jira Server and Confluence.

Example

If your license expires on the Aug 1st 2023, you may notice that Bitbucket displays a different date, such as the July 31st 2023 in Japan Standard Time (UTC+10). This is because your personal time zone is set to use your local time.

At the time of expiry (Aug 1st 2023), it will actually be the July 31st 2023 in Japan Standard Time. This license will be expired at July 31st 2023 23:00:00 in Japan Standard Time, it will actually be the Aug 1st 2023 00:00:00 in Australian Eastern Standard Time.