Release 9.x

Feature Release Summary

You can explore all the feature releases we’ve introduced to ScriptRunner for Jira, starting from version 7.0.0 onwards, on the Feature Release Summary page. This page is designed to assist you in finding the ideal version to upgrade to, all while catching up on any enhancements you might have missed since your last update.

9.19.0

 

New feature: Export scripts

We've introduced a new export feature in ScriptRunner. This feature allows you to export all scripts and configurations from your instance via the Script Registry, with the exception of Workflow scripts and ScriptRunner JQL function information.

In this context, "scripts" encompass a broader range of elements than typical custom script files. Specifically, we include:

  • All scripts within your script roots.
  • All configured custom and built-in Jobs, Listeners, Fields, Behaviours, UI Fragments, REST Endpoints.

See the Script Registry page for more information on this feature.

Thinking of migrating to Cloud?

This feature will help you analyze your instance and scripts in preparation for migration to Cloud.

New feature: Inbox

We have introduced a new Inbox feature in ScriptRunner. When enabled, it displays notifications about breaking changes, migrations, recommended upgrades, new releases, and other important updates. When disabled, no information displays in the inbox. See the In-App Communications page for information on how to enable/disable this feature.

Documentation update: Jira 11 search API migration guide

In Jira Data Center version 10.4, Atlassian has introduced a new Search API, marking a significant overhaul of the search functionality by transitioning from Lucene to OpenSearch. Some of your scripts may break when Jira 11 is released. To avoid any downtime in your scripts when you upgrade to Jira 11, we recommend you use our Jira 11 Search API Migration Guide to upgrade any affected scripts.

This guide is still a work in progress and may be updated in the coming weeks. We recommend you to bookmark the guide and check back regularly for the most up-to-date information.

Script Registry bug fixed

The Script Registry now correctly displays all workflow functions with scripts for each transition. Previously, only one function was shown per transition, even when multiple were set up.

9.18.0

 

Security Improvement

In this release, we've focused on improving the security of ScriptRunner for Jira by addressing a known Common Vulnerabilities and Exposure(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.

Update: Jira (10.3.4) Bug affecting HAPI

Affected Jira versions (10.3.4) and all ScriptRunner versions.

There is a bug in Jira that is affecting HAPI. When using issueInputParameters.setSkipScreenCheck(true) and certain custom field types, a NullPointerException occurs. We are working with Atlassian to resolve this bug (see JSDSERVER-16263), but we have a temporary workaround that can be applied in certain instances so that you can continue to use HAPI. Please note that updates to any field not on the relevant screen will be silently dropped, so this workaround is not suitable for all cases.

To check to see if you are affected, look for an NullPointerException with convertToSimpleEntry (line 2 below): 

groovy
java.lang.NullPointerException
	at com.atlassian.jira.web.action.issue.util.JiraFieldParamHelper.convertToSimpleEntry(JiraFieldParamHelper.java:92)
	at com.atlassian.jira.web.action.issue.util.JiraFieldParamHelper.lambda$convertToParam$0(JiraFieldParamHelper.java:54)
	at com.atlassian.jira.web.action.issue.util.JiraFieldParamHelper.convertToParam(JiraFieldParamHelper.java:56)

In every update and transition closure that is affected, add setSkipScreenCheck(false) (shown in line 3 here):

groovy
Issues.getByKey('JRA-1').update {
    summary = 'Updated summary'
    setSkipScreenCheck(false)
}

Updates to any field not on the relevant screen will be silently dropped, so this workaround is not suitable for all cases.

9.17.0

 

Behaviours bug fixed

We've resolved a bug related to our Behaviours feature where setFieldOptions() did not work correctly for Select List (cascading) fields on the JSM portal.

Documentation enhancement

We’ve updated our Rewriting Scripts for Cloud Hints and Tips page. This page provides step-by-step instructions, best practice tips, and examples to support your migration from Scriptrunner for Jira Server/Data Center to ScriptRunner for Jira Cloud.

9.16.0

 

Bugs fixed

We have resolved the following bugs in this release:

  • Behaviours bug: We fixed a conflict between setFieldOptions and setFormValue for multi-select fields.
  • Common-runtime module bug: We resolved an issue where ScriptRunner's common-runtime module interfered with fields from other plugins.
  • httpmime version update: httpmime version has been updated to version 4.5.14 to match the httpclient version. Previously, ScriptRunner for Jira had httpclient version 4.5.14 and httpmime version 4.3.1.

Vulnerability scanner updates

We have updated and added new vulnerability scanners to reduce discrepancies in your vulnerability reports. This is an internal feature and does not require any action from you.

9.15.0

 

Compatibility with Jira 10.6

We are now compatible with Jira 10.6. However, we have a known issue where custom group fields aren't properly indexed, causing inconsistent results when used in JQL queries. Atlassian is working on a fix, and we expect this issue to be resolved in a future release.

Security Improvement

In this release, we've focused on improving the security of ScriptRunner for Jira by addressing a known Common Vulnerabilities and Exposure (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.

9.14.0

 

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

9.13.0

 

Jira compatibility

ScriptRunner for Jira is now compatible with Jira 10.5.x.

Behaviours bugs fixed

We've resolved bugs related to our Behaviours feature. setFieldOptions() previously caused the following issues:

  • Disrupted setFormValue() in the JSM portal.
  • Caused errors when creating or editing issues in a Kanban board. 

These bugs are now fixed. 

9.12.0

 

Behaviours bug fixed

We've resolved a bug related to our Behaviours feature. This issue affected the setting of field options for radio buttons and checkboxes on the JSM portal.

9.11.0

 

Security Improvement

In this release, we've focused on improving the security of ScriptRunner for Jira by addressing a known Common Vulnerabilities and Exposure (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.

Behaviours bug fix

We have fixed a bug related to our Behaviours feature. Previously checkboxes and radio buttons weren't being hidden properly. This bug has been fixed, and these fields now function as intended, hiding correctly when specified.

Documentation update: Removal of legacy versions

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.

9.10.0

 

Jira compatibility

ScriptRunner for Jira is now compatible with Jira 10.4.x.

Library update: Example scripts have moved to ScriptRunner HQ

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.

This update does not affect in-app example scripts, which will continue to function as usual.

9.9.0

 

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

9.8.0

 

Security improvement

In this release, we've focused on improving the security of ScriptRunner for Jira by addressing known Common Vulnerabilities and Exposures (CVEs). 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.

New: In-app feedback

In this release, we have introduced a new feedback system to improve the way we gather user insights. You may encounter notifications linking to surveys, which offer a convenient method to share your thoughts about the product.

The notifications will not appear:

New: HAPI documentation

We have created a new page that explains how to Simplify Current Scripts with HAPI. The guidance explains why it's useful to simplify your scripts with HAPI, how to find scripts that can be simplified, and examples of simplified scripts. 

9.7.0

 

Jira compatibility

ScriptRunner for Jira is now compatible with Jira 10.3.0.

Behaviours bug fixed

Previously, when customers submitted requests through the customer portal, Behaviors did not function as intended. This issue has been resolved, and Behaviors now operate correctly within the customer portal.

9.6.0

 

Security Improvement

In this release, we've focused on improving the security of ScriptRunner for Jira by addressing a known Common Vulnerabilities and Exposure (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.

9.5.0

 

Configuration Manager for Jira (CMJ) compatibility

ScriptRunner for Jira is now compatible with Configuration Manager for Jira following the Jira 10.0 upgrade. 

Jira compatibility

ScriptRunner for Jira is now compatible with Jira 10.1.x.

9.4.0

 

Resources update

We have removed some visibility of passwords within Resources. This change is designed to enhance security by preventing credentials from being viewed by other Jira administrators. See SRPLAT-2672 for more details.

9.3.0

Jira 10.0 compatibility

We're now compatible with all versions of Jira 10.0. See SRJIRA-7537 for more information. 

Tempo compatibility

We are happy to confirm that ScriptRunner for Jira Data Center (version 9.1.1 onwards) is compatible with Tempo version 18.0.0-jira-10. 

New features

  • SRPLAT-2645 - HAPI Linter: Top 10 methods for autosuggestion
  • SRJIRA-7537 - Make ScriptRunner for Jira Data Center compatible with Jira 10.0.0
  • SRJIRA-7388 - Add method to recalculate Scripted Field value upon calling

Bugs fixed

  • SRPLAT-1209 - Setting REST endpoint package to scan to empty value does not work
  • SRJIRA-7547 - Behaviour: setFormValue() doesn't work for User Picker (Multiple Users) fields in Service Desk Portal when using Deutsch (Deutschland) - V8
  • SRJIRA-7546 - When language is Polish, Behaviour setRequired() message still shows even the Multiple User Picker field has value during creation in Customer Portal - Version 8
  • SRJIRA-7412 - Behaviours is not triggered when clearing the Assets field value 
  • SRJIRA-7170 - When language is Polish, Behaviour setRequired() message still shows even the Multiple User Picker field has value during creation in Customer Portal - V9

9.2.0

 

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

Upcoming Resources update

In a forthcoming release, we will be removing the visibility of passwords within Resources. This change is designed to enhance security by preventing credentials from being viewed by other Jira administrators.

9.1.1

Compatibility with Jira 10

ScriptRunner for Jira is now compatible with Jira 10. See the Compatibility with Jira page for more information on Jira 10 best practices on upgrading your instance.

Breaking changes

There are some key breaking changes you should be aware of when upgrading to Jira 10:

  • Third-party library/API removal
  • JDK has been updated. The minimum supported version of the JDK is now JDK 17. 
  • Fragments updates (see more below)

See the breaking changes page for the full details of all breaking changes related to this upgrade. 

Fragments updates

To adhere to Jira 10, UI Fragments had the following changes: 

  • Raw XML Module Breaking Change: Fragment XML conditions scripts and web panel class scripts are now provided via XML parameters and are no longer directly set as the condition class element attribute or the web panel class element attribute value. The previous formats no longer work in Jira 10 versions of ScriptRunner. You can use the Raw XML Module Breaking Change guide to help you convert your scripts to the new fragment XML parameters format. Major changes include: 
    • Format of the XML condition class attribute and user scripts now added as parameters
    • Format of the XML Web Panel class attribute and user scripts now added as parameters
Related documentation changes appear on Raw XML Module Built-In Script.
  • Web Panel Breaking Change/Deprecation for Jira 10: If you used a com.atlassian.plugin.web.model.WebPanel class implementation for the provider class/script of your web panels, the way this is processed will be different after upgrading to Jira 10. Check out the Web Panel Breaking Change/Deprecation for Jira 10 guide to learn how to update scripts. Major changes include: 
    • The writeHtml method is now ignored
    • The Atlassian com.atlassian.plugin.web.model.WebPanel interface is deprecated and has moved to a new location
  • Web Resource Breaking Change: If you have files in plugin.resource.directories you will have to move them to web-resources/com.onresolve.jira.groovy.groovyrunner. Check out the Web Resource Breaking Change page to learn more.

  • Web Item Provider Built-In Script: Major changes include:

    • The feature will only function once Jira releases the new fragment API updates (Estimated to be available from Jira 10.1.0/10.0.2). SRPLAT-2596
    • The com.atlassian.plugin.web.api.model.WebFragmentBuilder API has moved to com.atlassian.plugin.web.model.WebFragmentBuilder. Any scripts using the old API import will need to be updated to the new location. (Once updated, your scripts will no longer show a red line under the old import; however, you cannot verify the fix fully until Atlassian releases the API mentioned in the SRPLAT-2596.)

Backward compatibility

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

Tempo compatibility

ScriptRunner for Jira Data Center is currently not compatible with Tempo after the Jira 10.0 upgrade. We aim to be compatible with Tempo soon.

Bugs fixed

  • SRPLAT-2630 - Script compilation can leak file handles
On this page