Jira

Incidents in Jira feature is leaving soon

This Jira removal has been generally available on Atlassian Cloud since 28 Oct 2026. It removes existing functionality, so admins should check what depends on it before it reaches their sites.

Generally available since 28 Oct 2026
Medium impact
Admin review: removal

Read Atlassian's release note See every change

Where the rollout is

First published 29 Apr 2026 Done
Rollout starts 13 Jul 2026 Done
Generally available 28 Oct 2026 Done

What changed

29 Apr 2026 First published by Atlassian

Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.

Source Atlassian's release note Read it on the Atlassian Community

Related changes

Where it lands

Where this change sits on the Stack

Every change is sorted onto the layer it touches first. This one lands on Governance and Change.

Agents and Automation

Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.

Atlassian Anthropic

Governance and Change

Permission architecture, audit and compliance, ITSM and change control, change management, strategic reporting and budgets.

Atlassian Guard Jira Service Management Strategy Collection Jira Align

Platform and Migration

Migration of every kind, tool consolidation, licensing, standardization, the system of work.

Atlassian Miro AWS Azure

Identity and Access

Human and non-human identity, SSO, SCIM, least privilege, access reviews, Guard cleanup, Agent SSO readiness.

Atlassian Guard Okta

load-bearing, bottom to top

Find out what your controls would survive.

Fixed scope. The assessment looks at permission architecture, change control, and every place audit evidence is still assembled by hand. You get the findings, the ownership gaps, and the order to close them in.

Book the assessment

By sending this you agree to our privacy policy.

Not ready? Talk to an architect