Jira, Jira Service Management

Prevent people from downloading attached files

This Jira and Jira Service Management change has been generally available on Atlassian Cloud since 22 Oct 2026. Atlassian asks admins to prepare for it, and its release note lists what to do.

Generally available since 22 Oct 2026
Medium impact
Admin review: prepare for this change

Read Atlassian's release note See every change

Where the rollout is

First published 20 Mar 2025 Done
Rollout starts 11 Jun 2025 Done
Generally available 22 Oct 2026 Done

What changed

20 Mar 2025 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 Identity and Access.

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 who can reach what.

Fixed scope. The assessment starts at the identity layer: human and non-human access, the accounts nobody owns, and what has to be true before an agent gets one. 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