Disabled ScriptRunner validators/conditions enforced again after Connect→Forge workflow-rule switch

Incident Report for Adaptavist Cloud Apps

Identified

We have identified the root cause of an issue with the Workflow Rules service, causing validators and conditions that are disabled in ScriptRunner to be enforced by Jira again after a workflow is edited and published.
Workaround: in ScriptRunner → Workflows, Enable and then Disable the affected rule again, or delete it. This does not affect other rules.
Our engineering team is working with Atlassian on a fix and preparing a correction for rules already affected.
We’ll provide an update shortly.
We apologise for any inconvenience caused and thank you for your patience.
Posted Oct 09, 2026 - 18:43 UTC
This incident affects: ScriptRunner (ScriptRunner for Jira Cloud).