Resolved -
We have identified the issue and released a fix. Apologies for the inconvenience
Dec 19, 15:53 UTC
Monitoring -
All scripts are back to running as usual. We have introduced changes to our distributed cache system and scaled up to improve the availability.
Dec 19, 12:00 UTC
Investigating -
Some customer scripts are not running in the US region. This occurred between 19:00 and 21:50.
Dec 18, 19:00 UTC
Resolved -
We have confirmed that automated migrations are working properly. We have identified the root cause and putting things in place to prevent a future outage.
Dec 16, 14:28 UTC
Monitoring -
After some updates, we have observed the automated path for JCMA migrations to have returned. We are still monitoring the situation and working with Atlassian to ensure it is resolved across the board.
Dec 15, 14:17 UTC
Investigating -
Automated migrations of ScriptRunner config via JCMA may be bocked due to JCMA not discovering that ScriptRunner for Jira Cloud has an automated migration path.
Dec 12, 16:55 UTC
Resolved -
Scripts appear to have continued to perform at their standard level throughout a period of monitoring, therefore we're marking this incident as resolved.
Apologies for any inconvenience caused.
Dec 11, 09:52 UTC
Update -
The measures we deployed to address delays in script execution have been effective, and scripts are now running at normal performance levels. We will continue to monitor the application, and will mark this incident as resolved if no further issues are observed.
Dec 10, 19:58 UTC
Identified -
W've become aware of delays in script executions and are deploying a measure that should improve matters. We'll monitor its efficacy and update further.
Dec 10, 16:48 UTC
Resolved -
The issues we were seeing have now been resolved and filters are being synced automatically again.
Dec 10, 20:27 UTC
Investigating -
We are experiencing issues in filter syncing for ScriptRunner for Jira Enhanced Search customers in the US since 15:25 GMT. Some filter results may be out of date whilst we investigate what is happening. You can attempt to work around this by manually syncing the filter from the Enhanced Search page. We appreciate your patience as we investigate the issue.
Dec 10, 19:50 UTC