Atlassian has shipped a fix, which we have now applied, and this issue is resolved. Please let us know if you experience any further problems. Thank you for your patience
Posted Oct 27, 2026 - 20:23 UTC
Update
We expect a fix from Atlassian to be released by early next week. We will post another update once we confirm it resolves the issue.
Posted Oct 21, 2026 - 09:36 UTC
Update
We continue to discuss potential approaches with Atlassian, who are still investigating and working towards a fix.
We’ll provide another update when there is further progress or when Atlassian ships a fix. Thank you for your continued patience.
Posted Oct 20, 2026 - 10:41 UTC
Identified
We have identified the root cause of the issue with the Workflow Functions service, causing transitions to fail with "Action N is invalid" when a ScriptRunner "Restrict transition" condition checks a field that the same transition's screen fills in.
Atlassian has confirmed this is a defect in Jira Cloud: Forge workflow conditions are re-evaluated at execution time against the values just entered on the transition screen instead of the stored work item. It is tracked by Atlassian as https://jira.atlassian.com/browse/ECO-1851. The fix must come from Atlassian; we recommend watching and voting for that ticket.
Only conditions that reference a field on the transition's screen are affected. Validators and post functions are not affected.
We'll provide an update when Atlassian ships a fix.
We apologise for any inconvenience caused and thank you for your patience.
Posted Oct 12, 2026 - 16:09 UTC
This incident affected: ScriptRunner (ScriptRunner for Jira Cloud).