ScriptRunner audit log helps you to inspect the script configuration changes made by the users. The audit log service logs add, edit or delete operation for ScriptRunner scripts as part of application audit log. The service also logs execution of built-in scripts that could potentially change the system.

To avoid swamping the audit log, the service does not log activities where scripts read data from the system rather than changing the configurations.

View Audit Log

ScriptRunner audit logging is enabled by default since ScriptRunner v5.6.7 as part of the Bitbucket audit log present in repository and project settings. You must be a project administrator or repository administrator to vew the Bitbucket audit log.

Navigate to Repository settings → Audit log or Project settings → Audit log to view the audit log.

The Action column will be prefixed with 'ScriptRunner' for ScriptRunner related audit log entries. Entries that are not prexifed with 'ScriptRunner' will either be from Bitbucket itself or other installed apps.

The Details column will contain a JSON representation of the configuration related to the audit entry, this is convention for the Bitbucket audit log.

The Bitbucket audit log can only be viewed from within project or repisitory settings, there is no global audit log view that an administrator can access for an overview of all repositories and projects. A plain text audit log file is stored on disk which will contain all recent audit log entries. The audit log file can be found at the following path within the Bitbucket home directory: log/audit/atlassian-bitbucket-audit.log

audit log bitbucket

Disabling Audit Log

You won’t be able to inspect ScriptRunner script configuration changes if the audit logging is disabled. We highly discourage disabling ScriptRunner audit logging mechanism unless you have a strong reason.

The ScriptRunner audit log can be disabled by enabling a Bitbucket dark feature.

Atlassian does not document how to utilise dark features in Bitbucket, and no user interface for the configuration of dark features is present. The only way to enable a dark feature is by setting a JVM system property, currently Atlassian do not provide any documentation for how to configure this.

The following system property can be used to disable audit logging: -Datlassian.darkfeature.scriptrunner.audit.log.disabled=true

The above property must be appended to the JVM_SUPPORT_RECOMMENDED_ARGS field present in the Bitbucket startup script. On Linux/MacOS this script is named and on Windows this script is named start-webapp.bat.

Have questions? Visit the Atlassian Community to connect, share, and learn with other Atlassian users and experts, including Adaptavist staff.

Ask a question about ScriptRunner for JIRA, Bitbucket Server, or Confluence.

Want to learn more? Check out courses on Adaptavist Learn, an online platform to onboard and train new users for Atlassian solutions.