{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-08-22T03:33:29.207Z"
  },
  "data": {
    "id": "incident_statuspage_jira_4wt6sbfk5gvp",
    "slug": "jira-disrupted-automation-for-jira-triggers-not-running-for-some-customers-2026-01-06",
    "title": "Disrupted Automation for Jira triggers not running for some customers",
    "summary": "Disrupted Automation for Jira triggers not running for some customers",
    "status": "resolved",
    "severity": "major",
    "startedAt": "2026-01-06T05:18:20.457+00:00",
    "updatedAt": "2026-04-02T07:06:36.582+00:00",
    "resolvedAt": "2026-01-07T11:32:21.56+00:00",
    "provider": {
      "slug": "jira",
      "name": "Jira"
    },
    "affectedServices": [
      {
        "slug": "jira-authentication",
        "name": "Authentication & Administration"
      },
      {
        "slug": "jira-automation",
        "name": "Automation & Notifications"
      },
      {
        "slug": "jira-issues",
        "name": "Issues & Boards"
      }
    ],
    "links": {
      "html": "/incidents/jira-disrupted-automation-for-jira-triggers-not-running-for-some-customers-2026-01-06",
      "api": "/api/v1/incidents/jira-disrupted-automation-for-jira-triggers-not-running-for-some-customers-2026-01-06",
      "providerHtml": "/providers/jira",
      "alerts": "https://outagedeck.com/account?stack=jira&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Jira reported a major event for the affected tracked services.",
    "source": {
      "id": "source_jira_status",
      "kind": "official_api",
      "name": "Jira Status",
      "checkedAt": "2026-08-22T03:30:16.021+00:00",
      "officialUrl": "https://jira-software.status.atlassian.com",
      "statusPageUrl": "https://jira-software.status.atlassian.com"
    },
    "updates": [
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_3pl7kp5ft78d",
        "status": "investigating",
        "body": "We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.",
        "createdAt": "2026-01-06T05:18:20.545+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_jtqcc7bg7fb1",
        "status": "identified",
        "body": "We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available.",
        "createdAt": "2026-01-06T06:17:34.042+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_l4fqsmrkx79h",
        "status": "identified",
        "body": "Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.",
        "createdAt": "2026-01-06T07:58:55.934+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_fm4j8j8hp0vl",
        "status": "identified",
        "body": "Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted.\n\nSome automation rules using specific triggers failed to execute, causing rules to appear unresponsive.\n\nWe have identified the cause and we continue working on restoring the operations back to normal as soon as possible.\n\nIn the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule.\n\nWe will provide the next update in about two hours or sooner.",
        "createdAt": "2026-01-06T10:11:17.378+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_9g1cqt2nb1lc",
        "status": "identified",
        "body": "Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. \n\nThe cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible.\n\nWorkaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule.\n\nWe will provide the next update in about two hours or sooner.",
        "createdAt": "2026-01-06T12:19:22.737+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_65ztp9n9kl48",
        "status": "monitoring",
        "body": "Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online.\n\nCustomers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted. \n \nDuring Asia Pacific hours tomorrow, the team plans to replay historical events.\nTeam will continue monitoring. Next update will tomorrow.",
        "createdAt": "2026-01-06T14:04:32.556+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_bf538rzdz8v2",
        "status": "monitoring",
        "body": "We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected.\nWe will provide the next update in about two hours or sooner.",
        "createdAt": "2026-01-07T04:43:41.576+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_dxz3n5p6jknv",
        "status": "monitoring",
        "body": "We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours.\n\nBased on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier.\n\nWe will provide the next update once replaying the historical events is complete.",
        "createdAt": "2026-01-07T08:37:24.563+00:00"
      },
      {
        "id": "update_statuspage_jira_4wt6sbfk5gvp_ms2s501gtzt3",
        "status": "resolved",
        "body": "Rerunning the remaining Automation for Jira rules that failed for affected customers is complete.\nThis update resolves the issue.",
        "createdAt": "2026-01-07T11:32:21.56+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}