We are now in the process of contacting affected customers. As a fix for this has been released and tested 1 week ago and the issue should not be occurring anymore, marking this incident as resolved. This incident has been resolved.
Posted Oct 26, 2026 - 16:15 UTC
Update
A fix has been released that prevents this issue from occurring on workflows going forward. Rules that were already affected prior to the fix remain in a broken state, and we're continuing to work with Atlassian to identify the complete list of impacted customers
Posted Oct 16, 2026 - 13:38 UTC
Update
Updated: We are actively working with Atlassian on a fix. The workaround below still applies. We apologise for any inconvenience and thank you for your patience.
Posted Oct 12, 2026 - 16:08 UTC
Update
Edit: this update was posted incorrectly and has now been removed
Posted Oct 12, 2026 - 15:57 UTC
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 affected: ScriptRunner (ScriptRunner for Jira Cloud).