Why Bitbucket shows different license expiry dates than your invoice or accounts page
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
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.
Solution
Understanding license expiry date discrepancies due to time zones
Your license is set to expire at midnight on the specified date in Australian Eastern Standard Time (AEST), which is UTC+10. If your license is set to expire on August 1, 2027, it will actually expire at 00:00:00 AEST on that day.
If you are viewing this expiry date in a different time zone, such as Japan Standard Time (JST), which is also UTC+10, it might appear as July 31, 2027, at 23:00:00 JST. This is because the local time zone setting adjusts the display of the expiry time to match your current location.
Another example
In Central Standard Time (CST), which is UTC-6, this would translate to July 31, 2027, at 09:00:00 CST. Therefore, if you are located in a region observing CST, you would see the expiry date as July 31, 2027, due to the 16-hour difference between CST and AEST.
This means that while the actual expiration is at the start of August 1 in AEST, it is still the previous day in CST.
Therefore, while the license expiry remains consistent, the displayed date may vary based on time zone differences.
Support
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 updates.
This discrepancy also exists in Jira and Confluence.
Was this helpful?