Release 9.x

We've updated the Home page in ScriptRunner to make it easier to find the functionalities you need.

We've strengthened the validation and sanitisation of user-supplied content in ScriptRunner web interfaces. No action is required on your side, and this update does not mean your instance was vulnerable to security issues. We're always working to make ScriptRunner as safe as possible, and this update is part of that ongoing effort. Check out our page on Vulnerabilities and Security for more details on how we scan for vulnerabilities and common security concerns.

We've resolved a bug related to one of our Built-in Scripts. Group picker fields in the Add/Remove Watchers built-in script now correctly accept groups whose names contain #. Previously, entering a group with # in its name caused the group field to return an error instead of accepting the value.

We've resolved a bug related to Fragments. Enabling other apps alongside ScriptRunner no longer causes a Fragment Manager clash. Previously, enabling or disabling apps could trigger a RuntimeException: org/dom4j/Element error.

We've resolved a bug related to Script Export. Script exports now display the correct script count for all supported script types, including CQL Functions and Macros. Previously, exports sometimes reported a script count of 0 for these types, even when scripts were present because the exporter did not correctly handle the JSON structures used by these script types.

You may now access the Script Registry from the Tabs view in the Administration options.

The Script Registry allows you to search your ScriptRunner custom scripts, view type-checking errors or deprecation warnings, and export all scripts and configurations on your instance.

Export scripts from the script registry. You can export all ScriptRunner scripts, configurations, and custom fields from your instance, except ScriptRunner JQL function information.

• We fixed a bug that caused the Create Page macro to return an error when viewed anonymously.
• We resolved an unexpected error that appeared during configuration of the Update Macro built-in script.

As recommended by Atlassian, we added a new configuration option within the ScriptRunner settings for system admins to enable/disable custom CSS for macros, and have this disabled by default for all users.

• We have fixed a bug that caused the Choose Label macro to return an error when viewed anonymously.
• We have fixed a bug that caused the Enhanced Search information panel to shorten the quick search results pane and prevent it from using the full available height.

On September 17, 2025, we will be removing legacy versions of the documentation. This change is part of our efforts to simplify the customer experience and align with wider industry practices. From September 17 onward, there will be two versions of documentation:

• The previous version: As of September 17, that will be 8.x. All documentation updates that happened from 8.0 to 8.52 and beyond will be available in 8.x.
• The latest version: As of September 17, that will be version 9.24. All documentation changes that happened from 9.0 to 9.24 and beyond when we release in the future will be available in the latest version.

If you have a link saved with a version number, you will be redirected to 8.x or the latest version. If you have any questions or concerns, please contact us.

On September 17, 2025, we will be removing legacy versions of the documentation. This change is part of our efforts to simplify the customer experience and align with wider industry practices. From September 17 onward, there will be two versions of documentation:

• The previous version: As of September 17, that will be 8.x. All documentation updates that happened from 8.0 to 8.52 and beyond will be available in 8.x.
• The latest version: As of September 17, that will be version 9.24. All documentation changes that happened from 9.0 to 9.24 and beyond when we release in the future will be available in the latest version.

If you have a link saved with a version number, you will be redirected to 8.x or the latest version. If you have any questions or concerns, please contact us.

In response to new Atlassian security requirements, you can only switch a user identity using the Switch to a Different User built-in script. Identity switching functionality from User Management and Confluence administration has been deprecated.

We've made a couple of security improvements in this release:

• We have implemented a security improvement to our switch user feature. This update strengthens our protection against potential unauthorized account access.
• We've addressed a known Common Vulnerabilities and Exposures (CVE).

We want to emphasize that this update doesn't mean your instance was vulnerable to security issues. We're always working to make ScriptRunner as safe as possible, and this update is part of that ongoing effort. Check out our page on Vulnerabilities and Security for more details on how we scan for vulnerabilities and common security concerns.

The Rewrite Scripts for Cloud Guide is ready to help with your migration!

There are only core component changes in ScriptRunner for Confluence 8.42.0, so we do not have any new features or bug fixes to report.

We added a Migration Checklist to help get you started with migration to ScriptRunner for Confluence Cloud!

There are only core component changes in ScriptRunner for Confluence 8.41.0, so we do not have any new features or bug fixes to report.

In the next few weeks, we will be phasing out all 6.x.x and 7.x.x versions of our documentation from public access. While this change is not expected to impact most users, we recommend taking the following actions:

• Review your bookmarks: If you have any saved links to our documentation, please verify that they don't point to versions that will be removed.
• Update your references: Ensure that you're using the most current documentation version for your needs.

If you have any concerns, please contact our support team.

There are only core component changes in ScriptRunner for Confluence 9.11.0, so we do not have any new features or bug fixes to report.

There is a new built-in script example, Pages with nested macros, for the XPath Search in Pages built-in script. You can use this to find all pages with macros nested inside of other macros in your Confluence instance. Check out the documentation to find out more information about using the script.

Adaptavist Library has been renamed to Example Scripts and all scripts have been moved to their new home on the ScriptRunner HQ website. These example scripts now live alongside the tutorials, case studies and other content designed to help you get the most from ScriptRunner. For more information, check out our blog on this update.

ScriptRunner for Confluence Data Center is now compatible with Confluence 9. See the Compatibility with Confluence page for more information on Confluence 9 best practices on upgrading your instance.

ScriptRunner 9.0.0 will only support Confluence 9.0. and above and will not be backwards compatible with earlier Confluence versions. Critical bugs and security fixes will continue to be released for ScriptRunner 8.x.x. We recommend users on older versions of Confluence or ScriptRunner plan their upgrade to ensure access to the latest features, performance improvements, and security enhancements. We recommend following our Compatibility with Confluence page for information and recommendations on how to upgrade.

Check out the Breaking Changes page for major updates for Confluence 9.0.0 that affect ScriptRunner for Confluence Data Center. Major changes include:

• Gray APIs removed
• APIs removed
• Gadgets removed
• JDK upgrade