Skip to main content
Contact usBook your demo
ScriptRunner for Jira and Confluence are now compatible with platform 8
Share on socials
A Data Center icon is surrounded by an arrow which displays a progress bar heading towards the number 8
A photo of Ankur Sharma
Ankur Sharma
Published on 9 October 2025
ScriptRunner for Jira
ScriptRunner for Confluence
Data center icon

ScriptRunner for Jira and Confluence are now compatible with platform 8

Earlier this year, Atlassian announced the launch of Jira 11 and Confluence 10 for Data Center. Here’s what you need to know before upgrading ScriptRunner.
Earlier this year, Atlassian announced the launch of Jira 11 and Confluence 10 for Data Center. General access versions are now available and these upgrades are engineered towards improved security for Atlassian Data Center customers.
ScriptRunner for Jira Data Center and ScriptRunner for Confluence Data Center are now compatible with these latest versions.
Please note that ScriptRunner for Bitbucket is not yet compatible with Bitbucket 10.
A teal coloured exclamation mark inside a grey triangle with a heavy black border

Latest versions

Compatible with the latest versions:
• ScriptRunner for Jira Data Center is compatible with Jira Software 11.
• ScriptRunner for Confluence Data Center is compatible with Confluence 10.
Not yet compatible with the latest versions:
• ScriptRunner for Bitbucket is not yet compatible with Bitbucket 10.

Why should I upgrade?

Platform upgrades can include important security updates, new features and more efficient workflows. Upgrading to the latest version ensures you benefit from the most up-to-date security fixes and patches, and the latest feature enhancements. Moreover, you can future-proof your organisation with the technical help that Atlassian provides only to those on recent versions.

What do I need to do?

ScriptRunner is now fully compatible with the latest versions of Jira and Confluence, so when you are ready to upgrade, you can seamlessly upgrade ScriptRunner too.

Breaking changes

There are some breaking changes that may impact your scripts. Please read the breaking changes guides and update your scripts before you upgrade.

ScriptRunner for Jira

  • Key API changes
    • Search API upgrade
    • TrustedRequestFactory removal
    • Spring and Jakarta upgrade
Read the full breaking changes guidearrow icon

ScriptRunner for Confluence

  • Key API changes
    • TrustedRequestFactory removal
    • Spring and Jakarta upgrade
Read the full breaking changes guidearrow icon

Best practice for upgrading ScriptRunner

  1. Check compatibility: Before proceeding with the platform upgrade, ensure the ScriptRunner version installed is specifically compatible with the target Atlassian platform release.
  2. Test in staging: Never upgrade production environments directly. Instead, implement, test, and validate the upgrade in a non-production (staging) environment to identify and resolve breaking changes or disruptions.
  3. Review breaking changes: Assess ScriptRunner's release notes and upgrade guides (listed above) for breaking changes, API deprecations, or differences in script management, then update any custom scripts in line with new APIs.
  4. Develop and execute robust testing: Build a detailed upgrade and testing plan. Conduct thorough testing to ensure all scripts, automations, and integrations continue to function as expected after upgrading.
  5. Backup systems: Before starting the upgrade, create full backups of your Atlassian environments to allow recovery in case of issues.
  6. Plan for downtime: Schedule the upgrade and notify users, as major upgrades may require system outages.
  7. Seek support if needed: Contact ScriptRunner support or an Atlassian Solution Partner if you encounter any issues or to seek help with complex upgrades.

Platform 8 Documentation

ScriptRunner for Jira

ScriptRunner for Confluence