Skip to main content
Home page

ScriptRunner's move to Atlassian Forge

Illustration of three teal arrow lines converging into one, pointing upwards
Atlassian has established its Forge platform as the strategic future of app development on Cloud, and the older Atlassian Connect* platform will soon be retired. This means that all apps built for Atlassian Cloud products must be moved to Forge, including the ScriptRunner suite.
*This is not related to ScriptRunner Connect, which is a standalone SaaS platform and is unaffected by this change.
This page is the central hub for information and status updates around ScriptRunner's move to Forge, and will be kept up to date throughout the transition period so you can find what you need.
Updates will include:
  • Forge release availability for each ScriptRunner app
  • Any user-facing changes, and who will be affected
  • Key dates and milestones
  • Migration start and completion announcements
Pink circle with an information logo inside a dark teal speech bubble icon
Icon of a pink hammer hitting a teal anvil

What does moving to Forge mean for ScriptRunner?

All ScriptRunner Cloud apps will move to Atlassian Forge Remote by the end of 2026, ahead of Atlassian's established end of support date for the old Connect framework.
The following ScriptRunner apps are part of this program:
Moving ScriptRunner to Forge means continued support and updates beyond the Connect end-of-support timeline, as well as faster access to new Atlassian platform capabilities as they're released.
In short, this move keeps ScriptRunner fully supported on Atlassian Cloud and ready for what's next.
Pink hand in a handshake with a teal hand forming the silhouette of a heart icon

What you can expect

ScriptRunner's transition to Atlassian Forge is already well underway. Our commitment is to complete this move with minimal disruption to you. Your scripts, configurations, and automations are designed to keep working throughout.

A few things worth knowing in advance:
White arrow icon pointing right inside a teal circle
You may briefly see two ScriptRunner entries in your app lists in Jira and/or Confluence. Should this happen, it is temporary and will resolve with no action needed on your part—it is an expected side effect of rolling out a Forge version of the app while a Connect version is simultaneously being retired.
White arrow icon pointing right inside a teal circle
Anything you need to do will be communicated ahead of time. We'll contact you via the technical email address associated with your Atlassian and ScriptRunner licence, you'll see in-app messaging, and this page will also be kept up to date as a single source of truth.
White arrow icon pointing right inside a teal circle
Due to differences in the Forge platform, a small number of older event types are changing. If any of your configurations rely on an affected event, you'll see a notification in-app and we will also contact you directly with details and next steps. You won't need to audit this yourself.

Progress updates

How you access ScriptRunner for Confluence Cloud has changed
Confluence
ScriptRunner for Confluence
1 September 2026

How you access ScriptRunner for Confluence Cloud has changed

As part of ScriptRunner's ongoing move to Atlassian's Forge platform, the in-app navigation and how you access the app has now changed.
Read more
Behaviours has integrated with ScriptRunner for Jira Cloud
ScriptRunner for Jira
Cloud
3 August 2026

Behaviours has integrated with ScriptRunner for Jira Cloud

ScriptRunner Behaviours is now available within the main ScriptRunner for Jira Cloud app. See what's changed.
Read more
Upcoming changes to Enhanced Search
Enhanced Search for Jira
Cloud
11 March 2026

Upcoming changes to Enhanced Search

Enhanced Search is moving to Atlassian's native Forge platform for improved security and usability. You can begin reviewing your existing saved filters for Forge compatibility ahead of the new app version launch.
Read more

Planned timeline

Phase one: Planning and preparation

Assessment of our Connect apps, migration strategy, and technical validation on Forge.
✅ Completed
Dark teal blueprint icon with white lines on it

Phase two: Development and migration

Incrementally moving ScriptRunner functionality to Forge Remote, with internal testing and compatibility checks.
🔧 In progress
Code block style text within a ScriptRunner panel

Phase three: External rollout

Releasing Forge-based versions to customers, with gradual adoption and close monitoring.
🔧 In progress—ongoing throughout 2026
Half a grey cog icon, with various coloured arrows pointing up out of the half-cog

Phase four: Completion

All ScriptRunner Cloud apps fully on Forge Remote; Connect dependencies removed.
🗓️ Scheduled to complete before Atlassian's Connect end of support (January 2027)
Icon of a browser window with a rocket inside it

Further help and support

If you have questions about ScriptRunner's move to Forge or the status of a specific app, we're here to help.