To Product Updates Hub
An update on ScriptRunner's move to Forge
Jessie Wang
15 October 2026
Read in 3 min
ScriptRunner's Cloud products are migrating from Atlassian's Connect framework to Atlassian's Forge platform. Due to unforeseen bugs and limitations on Forge, we are experiencing unexpected disruptions to some product functionality during this transition. Resolving the underlying platform issues requires fixes from Atlassian. We are working closely with their team to progress these fixes as soon as possible and minimise disruption.
ScriptRunner's Cloud products are currently being migrated from Atlassian's Connect framework to Atlassian's Forge platform. Due to unforeseen bugs and limitations on Forge, some customers are experiencing disruptions during this transition, including delayed script execution and previously disabled workflow rules becoming re-enabled.
Resolving the underlying platform issues requires fixes from Atlassian. We are working closely with their team to progress these fixes as soon as possible and minimise disruption.
Incident status updates
To keep up to date with ongoing incidents, including status updates, fixes and workarounds, please visit the status page. This page is always up to date with the latest information on all incidents. There is a subscribe button at the top of the page to keep informed about ongoing incidents, and also a subscribe button for each individual incident, so you can stay up to date on any that are directly impacting you.
To track Atlassian’s underlying issues, see the following work items:
JRACLOUD-99820 - Disabled workflow rules becoming re-enabled
What customers may experience:
Previously disabled workflow rules may become re-enabled when a workflow is saved or published. This can block transitions or hide transition buttons.
Workaround:
In ScriptRunner → Workflows, enable the affected rule, then disable it again. Alternatively, delete the rule if it's no longer needed. Other rules are not affected.
ECO-1851 - Workflow conditions evaluated incorrectly
What customers may experience:
A transition fails with the error "Action N is invalid" when a ScriptRunner "Restrict transition" condition checks a field that the user updates on the transition screen. Jira checks the condition against the newly entered value rather than the saved one. Validators and post-functions are not affected.
Workaround:
No workaround is available yet. The resolution requires a fix from Atlassian.
ECO-1848 - Delayed event and post-function execution
What customers may experience:
Workflow post-functions and script listeners may run several minutes after the triggering event, particularly at busy times. Post-functions on the same issue may also run in a different order than expected.
Workaround:
No workaround is available. The resolution requires a fix from Atlassian.
Why are we moving to Forge?
Atlassian has announced the retirement of Connect, the framework many Jira and Confluence Cloud apps were built on, with support ending in January 2027. It is therefore essential for all Atlassian apps to be rebuilt on their new platform, Forge, before January to ensure they remain secure and supported.
The following ScriptRunner apps are part of this program:
- ScriptRunner for Jira Cloud
- Enhanced Search for Jira Cloud
- ScriptRunner for Confluence Cloud
We apologise for the disruption that has been caused by this migration. We remain committed to moving to Forge as quickly and securely as possible to prevent further disruption.
If you have any questions or concerns about ScriptRunner's move to Forge or any of the incidents arising as a result of this migration, please do not hesitate to contact us.
Thank you for your patience and ongoing support.
How did you find this update?
Incident status updates
To keep up to date with ongoing incidents, including status updates, fixes and workarounds, please visit the status page.