Important Instructions

If you are currently using either version 5.4.16 to 5.4.22 and you are moving to the latest release, you may experience issues updating if you are using ScriptRunner dependent plugins and they are enabled. There are workarounds documented as part of SRCONF-439.

Workaround

You can avoid this issue simply by disabling dependent plugins BEFORE you update ScriptRunner. You can then simply update ScriptRunner and re-enable your dependent plugins. Once you update to 5.4.26 or later, you will no longer need to perform this workaround.

Features

  • [SRCONF-334] - Add a script to set page restrictions recursively
  • [SRCONF-314] - Create a new Rename Pages built-in script

Bugs

  • [SRCONF-285] - JS and CSS files are not working, has to be inline
  • [SRCONF-445] - ScriptRunner macros not present in Macro Manager

Compatibility

Adding Compatibility with Confluence 6.11.x

For how-to questions please ask on Atlassian Answers where there is a very active community. Adaptavist staff are also likely to respond there.

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