Release 10.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.

Try our migration tools!

The ScriptRunner Migration Suite (SMS) is a suite of tools that helps you plan, analyse, convert and deploy scripts with confidence, significantly reducing the manual migration effort. It supports (not replaces) your expertise. The suite is made up of three tools: 

  • ScriptRunner Migration Analyse and Assess Tool: Use this tool to review your ScriptRunner Data Center scripts and configurations for risks and cloud readiness.
  • The ScriptRunner Migration Agent: Use our specialised AI chat agent to create, convert, and optimise scripts, or you can use it to answer a variety of different questions about ScriptRunner.
  • ScriptRunner Dev and Deployment Tool: Use this tool to organise and deploy ScriptRunner Cloud scripts. It is focused on making it easier and faster for consultants and developers to migrate, test, and deploy scripts from ScriptRunner DC to Cloud.

If you have any questions, need help, or would like to request access to SMS, the quickest way to get assistance is through our dedicated support portal.

10.11.1

 

Insight events fix rolled back

We’ve temporarily reverted the Insight events fix introduced in 10.11.0, as this caused an OSGi bundling error that prevented the plugin from being enabled. 

10.11.0

 

Compatibility with Jira 11.3.6

We are now compatible with Jira 11.3.6. 

UserMessageUtil bug fixed

We’ve fixed an issue where messages created with UserMessageUtil weren't displayed until the page was refreshed because the relevant Jira events weren't firing. UserMessageUtil messages now appear correctly when triggered, without requiring a full page reload. See our custom post function documentation for more information on UserMessageUtil. 

Database picker bug fixed

We've fixed an issue where multi-select database picker fields did not render their values correctly in Column view. Multi-selection database picker fields now display their selected values as expected.

Insight event scripts bug fixed

We’ve fixed an issue where scripts importing Insight event classes, such as InsightObjectEvent or InsightObjectUpdatedEvent, failed to compile and run when those types were used explicitly. These scripts now save and execute correctly.

10.9.0

 

Script export improvement: saved JQL filters

Saved JQL filters that use ScriptRunner JQL functions are now included in the Script export. These filters are listed in the main Output.csv file, and each one is also exported as a .json file in the jqlFunctionFilters folder. Saved filters that do not use ScriptRunner JQL functions are excluded from the export.

Behaviours bug fixed

We’ve fixed an issue where certain Behaviours saved in older ScriptRunner versions (using a <parameters>{}</parameters> configuration) caused the Behaviours page to fail to load after upgrading to Jira 10. These legacy configurations are now handled correctly during upgrade, so the Behaviours page loads as expected without requiring manual edits.

HAPI bug fixed

We’ve fixed an issue in Jira Service Management where HAPI sometimes resolved request types using the service desk ID instead of the portal ID. In projects where these IDs differ, this could result in request types from the wrong project being displayed when setting or suggesting a Request Type. Request types are now consistently resolved by portal ID, ensuring the correct project’s request types are used.

Script export bug fixed

We’ve fixed an issue where the Script export omitted Groovy source files from ScriptRunner script plugins. Plugin-backed scripts are now correctly included in the export.

10.8.0

 

Script export bug fixed

We've fixed an issue with script export where a single invalid workflow (for example, a transition pointing to a nonexistent step) caused workflow configuration export to fail for all workflows, resulting in an IllegalStateException/CacheException. Export now skips only the invalid workflow and succeeds for the rest.

JQL custom function bug fixed

We’ve fixed an issue where custom JQL functions were not immediately available on all nodes after being scanned on a single node. Custom JQL functions scanned on one node are now propagated correctly, allowing end users to use them across the entire cluster without additional steps.

10.7.0

 

Behaviours bugs fixed

We’ve resolved multiple bugs related to our Behaviours feature:

  • Behaviours now execute correctly when creating issues via the .../secure/CreateIssue.jspa URL. Previously, changing a project on this URL did not trigger a Behaviour correctly.

  • Fields set to read-only via a server-side Behaviour are now correctly enforced when accessed using Jira quick actions/keyboard shortcuts (gg or .). Previously, if a field had no value, it remained editable via shortcuts even when configured as read-only.

10.6.0

 

Compatibility with Jira 11.3.2

We are now compatible with Jira 11.3.2. 

Script Fields bug fixed

We've resolved a bug related to our Script Fields feature. Script Fields using the Duration template now correctly display the formatted duration value. Previously, the literal text $DateUtils.formatDurationPretty($value) was shown instead of the actual duration.

10.5.0

 

Compatibility with Jira 11.3

We are now compatible with Jira 11.3.x. 

10.4.0

 

Compatibility with Jira 11.2

We are now compatible with Jira 11.2.x. 

Instance audit enhancement

We've improved the performance of our Instance Audit feature, ensuring faster and more reliable operation on larger Jira instances.

10.3.0

 

Compatibility with Jira 11.1

We are now compatible with Jira 11.1.x. 

Script export improvements

We've made the following improvements to our Script export feature:

  • ScriptRunner metadata is now included. The export now contains the ScriptRunner version, ScriptRunner app key, and Jira (host application) version. This information is stored in a .json file in the Instance information folder.
  • Legacy and duplicate workflow functions are now exported. Previously, these workflow functions were not included and would be missing from the export. They now appear alongside all other workflow functions.

10.2.0

 

Instance audit bugs fixed

We have resolved bugs related to our Instance Audit feature:

  • The App custom fields count displays correctly in the audit summary. Previously, the App custom fields count did not display as expected.
  • The Export Report button creates a download file as expected. Previously, in some unique instances of Jira, this button did not generate a CSV download file.  

Script export bugs fixed

We've resolved the multiple bugs related to our Script export feature:

  • The Export active scripts Only option now works as expected for all features. Previously, it did not export behaviours and listeners as expected. 
  • Resource names now display in the export. Previously, the names of resources did not display. 

10.1.0

 

Instance Audit built-in script is now available for ScriptRunner 10.x 

Previously, this built-in script was only compatible with ScriptRunner 9.25+.

Our Instance Audit built-in script enables you to quickly assess the current state of your Jira environment for easy cleanup, instance optimisation, and migration preparation. You can also use the Export report button to download CSV files containing more information on users, projects, custom fields, and workflow functions. See the Instance Audit documentation for more details. 

GIF of the instance audit feature

10.0.0

 

Compatibility with Jira 11 (with OpenSearch exception)

ScriptRunner for Jira is now compatible with Jira 11. For guidance on Jira 11 upgrade best practices and compatibility information, refer to our Compatibility with Jira page.

OpenSearch exception

Atlassian introduced a new OpenSearch opt-in feature in Jira 11. ScriptRunner for Jira is not currently compatible with this feature. To maintain ScriptRunner functionality, we recommend that you do not opt into OpenSearch. We are working on compatibility and will provide an update when support becomes available.

Backward compatibility

ScriptRunner 10.0.0 will only support Jira 11.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 9.x.x and 8.x.x. We recommend users on older versions of Jira or ScriptRunner plan their upgrade 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.

Breaking changes

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

  • TrustedRequestFactory removed in Jira 11: com.atlassian.sal.api.net.TrustedRequestFactory has been removed and will no longer work. Instead, use the HAPI class com.adaptavist.hapi.platform.oauth.OAuthRequestSigner to construct HTTP requests. See our Work with OAuthRequestSigner HAPI documentation for examples. 

  • Search API upgrade: Several methods from the current API have been removed. Lucene-specific API and components have been removed in favor of the platform-agnostic search API. 

  • Spring and Jakarta upgrade: Jira has upgraded to Spring 6.x and Jakarta EE 10.

  • jQuery upgrade: Jira has upgraded to jQuery 3 from version 2.

Scripts using upgraded or removed APIs may fail. For full details on all breaking changes and guidance on updating your scripts, see the breaking changes documentation.

On this page