Adaptavist Cloud Apps incident
Automated migrations using JCMA are blocked due to ScriptRunner for Jira cloud appearing to not have an Automated migration path
Resolved after 3 days 21 hours, affecting ScriptRunner for Jira Cloud, on December 12, 2025.
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.
Affected components
Update timeline
- investigating Dec 12, 2025, 04:55 PM UTC
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.
- monitoring Dec 15, 2025, 02:17 PM UTC
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.
- resolved Dec 16, 2025, 02:28 PM UTC
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.
Your product runs on more than Adaptavist Cloud Apps
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services