Heads up! ScriptRunner documentation is moving to docs.adaptavist.com. Adaptavist will keep this site up for a bit, but no future updates to documentation will be published here. ScriptRunner 6.20.0 will be the last release to link to scriptrunner.adaptavist.com for in-app help.

The ScriptRunner audit log helps you inspect the script configuration changes made by your users. The audit log service logs add, edit, or delete operations 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. It only logs activities where the configuration has been changed. Also, the service does not monitor JIRA workflow modification activities as JIRA already has its own mechanism in place to log such changes.

View Audit Log

ScriptRunner audit logging is enabled by default since ScriptRunner v5.3.8 as part of JIRA audit log. You must be a JIRA administrator to view the JIRA audit log.

Navigate to System →Audit Log to view the audit log. The Summary field appends with 'ScriptRunner' for the ScriptRunner audit log entry. The screenshot below is an example of how the ScriptRunner audit log entries looks like in JIRA audit log.

audit log jira

Disabling Audit Log

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

To disable the audit logging, follow these steps:

  • Login as an administrator and go to [BASE-URL]/secure/SiteDarkFeatures!default.jspa

    1. In the Enable Dark Feature text field, add scriptrunner.audit.log.disabled.

The image below shows the dark feature page after adding the scriptrunner.audit.log.disabled key :

audit log dark

Enabling Audit Log

  • Login as an administrator and go to [BASE-URL]/secure/SiteDarkFeatures!default.jspa

  • Locate scriptrunner.audit.log.disabled key and select (Disable) link on the right side of the key. This should remove the scriptrunner.audit.log.disabled key from the list.

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.