Important Update Effective February 1, 2024!
Due to recent changes in Jira and Confluence, we've made the tough decision to discontinue the OpenID Connect (OIDC)/OAuth app and no longer provide new versions for the newest Jira/Confluence releases as of January 31, 2024.
This is due to some necessary components no longer shipping with Jira/Confluence, which would require some extensive rewrites of the OIDC App.
Important Update! This app will be discontinued soon!
Due to recent changes in Jira, which no longer ships with some components required for our Read Receipts app to run, we've made the tough decision to discontinue the app, as of Februar 5, 2025.
Important Update! This app will be discontinued soon!
We've made the tough business decision to discontinue the app, as of January 11, 2025.
User Profile System-V Timezones Not Supported
System-V timezones are considered legacy and thus are not supported by the API Token Authentication app. Users with the Create & Delete Token On Behalf Permission can select presets to filter tokens, and timezone conversion is required to render these presets. The below describes how to deal with problems when still having a System-V timezone selected.
Before Version 2.7.2
Some users might see the below error when accessing the API Token UI; changing the timezone to a non-SystemV equivalent will fix that.
This is most likely because they have selected a SystemV-type timezone in their profiles:
Version 2.7.2+
Starting with version 2.7.2, users who selected a SystemV-type timezone in their user profiles will see a warning message in the Token Manager tab:
We are only aware of this being a problem in Bitbucket. Since the problem only affects users with the Create & Delete Token On Behalf Permission, only those users can see the warning above.
Here's how to change the timezone:
- Click on your user avatar and open Manage Account (1)
- Change the Time zone (2) to something which is not of type SystemV