Adaptavist Cloud Apps incident

Automated migrations using JCMA are blocked due to ScriptRunner for Jira cloud appearing to not have an Automated migration path

Minor Resolved View vendor source →

Adaptavist Cloud Apps experienced a minor incident on December 12, 2025 affecting ScriptRunner for Jira Cloud, lasting 3d 21h. The incident has been resolved; the full update timeline is below.

Started
Dec 12, 2025, 04:55 PM UTC
Resolved
Dec 16, 2025, 02:28 PM UTC
Duration
3d 21h
Detected by Pingoru
Dec 12, 2025, 04:55 PM UTC

Affected components

ScriptRunner for Jira Cloud

Update timeline

  1. 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.

  2. 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.

  3. 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.