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.
How can we monitor configuration changes?
Please note, starting with version 3.x., only Jira 9.2 and Confluence 7.20 and upwards support writing to the audit log. This is due to the audit log multi-platform code by Atlassian, that is needed for Jira 10, please see https://bitbucket.org/atlassian/platform-module-usage/wiki/auditing.md.
However, you can still find the author and data of the change in the database table as described below.
Since version 2.1.x, configuration changes are noted in the audit log of Jira/Confluence.
Additionally, you can see the user who did the change, e.g.
Additionally, you can find the information by running the following database query:
select "LAST_MODIFIED_BY", "LAST_UPDATED" from "AO_F58FCA_ALBA_CONFIG" order by "ID" desc limit 1;
Output:
LAST_MODIFIED_BY | LAST_UPDATED
------------------+---------------
admin2 | 1637851297239
LAST_MODIFIED_BY refers to the username and LAST_UPDATED is the unix timestamp of when the change was saved. You can use websites like https://www.unixtimestamp.com/index.php to convert the timestamp