Release 7.x

Modified Update Page Restriction Built-In Scripts

The Update Page Restrictions Confluence Administration and Update Page Restrictions Space Administration built-in scripts were also renamed. Additionally, the Permission Level field was renamed to Restriction Level. The script functions the same as it did previously.

New Settings Option

You can now show or hide the Enhanced Search section message.

Bugs Fixed

• ClassGraph ThreadGroup memory leak (SRPLAT-2253)
• Copy Space script return stacktrace if user do not have Create Space(s) permission (SRCONF-2532)
• Enhanced Search banner for other languages (SRCONF-2319)

Documentation Update

Permissions has been added to the documentation to list the different features of ScriptRunner for Confluence and what user permissions are needed to use it.

Documentation Update

Java Agents and ScriptRunner has been added to the documentation to help you use Java Agents with ScriptRunner for Confluence.

Hide the binocular icon

You can now show or hide the Enhanced Search binocular icon.

Package declaration message

In version 7.1.0, we introduced a warning message to the Script Editor to flag invalid/missing package declarations in script files. The message stated these invalid/missing package declarations wouldn't be supported from version 9.0.0 onwards. However, this is no longer the case. We will not do anything that breaks existing usage in future releases. See this page for more information.

New Features

• Add an ability to disable/hide the binocular icon from Enhanced Search (SRCONF-2259)

Bugs Fixed

Bulk Purge Trash Job

You can now use the Bulk Purge Trash job to create a job that runs on a set schedule to purge the trash from all the spaces specified in the job.

Bugs Fixed

• The code in the editor disappears when switching between the script editor tab and other SR tabs (SRPLAT-2059)

New switch user functions

Administrators can now switch to a different user from within a page in Confluence or in the User management space. Previously admins could only switch user through the Switch User built-in script.

New Features

• Documentation shown when we hover over import keyword in an import statement (SRPLAT-2070)
• Automatically add a package declaration when a new file is created using script editor to avoid package name mismatch (SRPLAT-2058)

Bugs Fixed

• open redirect vulnerability (SRPLAT-2097)
• Fragments Custom Web Item link "mailto:" not working (SRPLAT-2080)
• Web items - URISyntaxException: Illegal character in query (SRPLAT-2028)

New user setting allows toggling the minimap on/off

The minimap is visible on the right-hand side of your script. When you write a script, the minimap can be useful for navigating, and understanding, large areas of code. You can now turn the minimap off if you don't find it useful! See the User Editor Settings page for more information.

New Features

• more tolerant parser strategy to allow completions in syntactically incorrect code (SRPLAT-2055)
• warn if package declaration is incorrect/missing when editing a file script (SRPLAT-2047)
• Add settings page available to all users with minimap toggle slider (SRPLAT-2001)

Bugs Fixed

• Unable to load list of slack channels if scopes to access private channels is missing. (SRPLAT-2073)
• prevent script engine making unnecessary "file open" operations (SRPLAT-2068)
• console script to test filesystem performance (SRPLAT-2063)
• Slow Disk Access for Script Roots can lead to stuck thread errors under high load (SRPLAT-1922)
• Page tree options are shown as expanded although no options displayed (SRCONF-2347)
• Copy Space script does not copy Space's Colour Scheme (SRCONF-1887)
• Adding the Create Page macro to a table header results in an error (SRCONF-1514)

Groovy 3 update

This is the update you've all been waiting for. We have updated ScriptRunner for Confluence to Groovy 3! What comes with this update and how will it benefit you?

To start, the language parser has been reimplemented in Groovy 3 under the Parrot Parser codename. This new parser brings a number of syntax improvements that could benefit you as a user of ScriptRunner. The Groovy 3 syntax improvements include the following:

• Improvements that bring Groovy syntax closer to that of modern Java, such as interface default methods, Java style lambda syntax, Java style method references, or try-with-resources statements.
• Additional operators, for example !in and !instanceof, === and !== for identity comparison or null safe subscript operator.

In addition, there are a handful of minor general improvements, for example, new GDK methods or the @NullCheck AST transformation .

For a full list of changes, see the release notes for Groovy 3.

Breaking changes

There are a number of known breaking changes in Groovy 3. The breaking changes include relocation of some classes to different packages. All the other breaking changes for Groovy 3 are listed in the release notes. There are also some additional minor breaking changes in Groovy 3.0.5. and Groovy 3.0.8.

We don't believe that any of these changes are significant, or that they should affect a large number of ScriptRunner users. However, there is a chance this update may cause some of your scripts to fail.

If you have any issues, please contact our customer support team here.

SrSpecification has been deprecated

In the past, when writing tests, we provided an example to extend com.onresolve.scriptrunner.canned.common.admin.SrSpecification.

SrSpecification will be removed in a future release of ScriptRunner, but is still available in the current release. From now on, please use spock.lang.Specification as the base for your tests.

Lock Content macro has been removed

We deprecated the Lock Content macro in release 6.27.0, and gave notice then that the macro would be removed in a future release. That is now happening with the release of 7.0.0.

You can check to see if the Lock Content macro is used on any of your pages by using Enhanced Search and searching for macro = "lock-content-macro". This returns a list of any pages that use the macro.

You can then decide how to handle the removal of the macro from each page. You could, for example, change the page permissions. Or you could move the content to a secured page and use the Include Page macro.

If you have issues related to the removal of the macro, please contact us via our support portal for assistance. If you have a request for functionality similar to the Lock Content macro, please open a new feature request with Support. By creating these requests, we can better understand your use case and help you solve problems.

Jsoup update

We have updated our internal version of Jsoup to 1.15.3 due to a potential vulnerability. The key change is the replacement of org.jsoup.safety.Whitelist with org.jsoup.safety.Safelist. Please find more information at https://jsoup.org/news/release-1.15.1.

New Features

• Update to Spock 2.0 (SRPLAT-2005)
• Change field description label so it is above snippets/examples (SRPLAT-1999)
• Upgrade to Groovy 3.0.12 (SRPLAT-1954)

Bugs Fixed

• Inner class in Script Editor causes autocomplete to fail and errors output in server log (SRPLAT-2027)
• Import statement mangled when package declaration present (SRPLAT-2007)
• Automatic import completions are mangling imports in some cases (SRPLAT-1991)
• Documentation for wrong method shown when using property setter shorthand (SRPLAT-1983)
• Static Type Checking may lead to large consumption of memory in some circumstances (SRPLAT-1923)
• Lock content macro not hiding content in edit page mode (SRCONF-824)