Release 7.x
Check out what's new with ScriptRunner for Confluence!
7.5.0
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
Bugs Fixed
7.4.0
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
7.3.0
ADVANCE NOTICE
Beginning in ScriptRunner for Confluence 8.0.0, existing Custom Search Extractors will no longer function. This is due to the requirement that we must move to the new Extractor2 implementation in order to maintain cross-compatibility with Confluence 7.x.x and Confluence 8.x.x. Existing Search Extractors cannot be automatically migrated and manual intervention by customers will be required.
We aim to provide feature parity with the new Extractor2 implementation along with documentation describing how to migrate your existing extractors. Our goal is to have the new Extractor2 implementation released in ScriptRunner for Confluence 8.0.0, or in a version shortly after that.
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
Bugs Fixed
7.2.0
New user setting that allows you to toggle the minimap on and 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
Bugs Fixed
7.1.0
New Features
Bugs Fixed
7.0.0
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
!inand!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
Bugs Fixed