Adaptavist Cloud Apps Status

Identified: We are now working with Atlassian on a fix. We’ll provide an update shortly. Thank you for your patience.

Identified: We are still continuing to work on a fix for this issue and advise any customers affected by this issue to use the workaround provided in our previous update.

We apologise for any inconvenience caused by this issue.

Identified: We are continuing to work on a fix for this issue that prevents workflows with large scripts from loading. We advise all customers experiencing this issue to edit the affected post function using the Workflows Admin page. Once on this page, we advise you to copy the script and add it to Script Manager as a script file. After doing this, you can then replace the inline script with the script file, which will reduce the post function size and allow it to start loading correctly again in the Jira Workflow.

Identified: We have identified the issue and isolated it to the post functions with very large scripts. Affected users can continue to edit scripts using the Script Runner Workflows page. Our team is actively working on a solution. We apologise for the inconvenience and appreciate your patience.

Identified: We have identified the issue and have reported it to Atlassian to resolve it. We will update this page when there is a change.

Investigating: We are investigating issues with the workflow edit page not loading.

Resolved: We have identified that event processor EU froze in the morning of 2nd October, losing events affecting multiple customers

Resolved: We have identified that script listeners timed out approximately between 7 pm UTC on Oct 2 and 1 am UTC on Oct 3 due to the events spike from 1 customer, affecting other customers

Identified: We can confirm that Atlassian have confirmed that the source of the delays is being caused by them sending us the events late.

We are awaiting Atlassian to implement a fix for this issue and will provide an update once they have done this.

Identified: We have identified that workflow post functions are executing late because post function invocation events are being delivered late to ScriptRunner by Atlassian's Forge platform. We have raised this with Atlassian and are awaiting their investigation. We’ll provide an update shortly. We apologise for any inconvenience caused and thank you for your patience.

Identified: Correction: the update posted on 12 October at 15:57 UTC was intended for a different incident and does not apply here. This incident, ScriptRunner validators and conditions that were disabled being enforced again after a workflow is edited and published, remains open. We are still working with Atlassian on a fix and on correcting rules already affected. The workaround above still applies. We apologise for the confusion.

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.

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.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We have identified the root cause, the issue only affects connect admin pages

We have identified the root cause: this issue only affects the Connect admin pages.

Workaround: Please use the Forge ScriptRunner admin pages instead. You can access them via the Apps sidebar:

1. In the sidebar, select the top ScriptRunner app.
2. Look for the Forge admin pages, which feature a cog icon to the left of each page name.

Investigating: We've identified an issue where admin pages are not loading for a subset of customers, we are investigating a fix for this now

Apologies for any inconvenience caused

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.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We have identified the root cause, the issue only affects connect admin pages

We have identified the root cause: this issue only affects the Connect admin pages.

Workaround: Please use the Forge ScriptRunner admin pages instead. You can access them via the Apps sidebar:

1. In the sidebar, select the top ScriptRunner app.
2. Look for the Forge admin pages, which feature a cog icon to the left of each page name.

Investigating: We've identified an issue where admin pages are not loading for a subset of customers, we are investigating a fix for this now

Apologies for any inconvenience caused

Resolved: We have identified that event processor EU froze in the morning of 2nd October, losing events affecting multiple customers

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We have identified the root cause, the issue only affects connect admin pages

We have identified the root cause: this issue only affects the Connect admin pages.

Workaround: Please use the Forge ScriptRunner admin pages instead. You can access them via the Apps sidebar:

1. In the sidebar, select the top ScriptRunner app.
2. Look for the Forge admin pages, which feature a cog icon to the left of each page name.

Investigating: We've identified an issue where admin pages are not loading for a subset of customers, we are investigating a fix for this now

Apologies for any inconvenience caused