Skip to content
Talk to an architect
Jira Service Management, Jira

Field schemes: A new way to manage fields

This Jira Service Management and Jira change has been rolling out to Atlassian Cloud sites since 17 Jun 2026. Atlassian rates its impact high, so admins should review it before it reaches their users.

  • Rolling out since 17 Jun 2026
  • High impact
Read Atlassian's release note See every change

Where the rollout is

  1. First published Done
  2. Rollout starts Done
  3. Preview track Done
  4. Bundled track Next

What we would do

New custom fields no longer attach to every space automatically, so each field gets associated on purpose. Inventory your field configurations before the switch and retire the ones nobody uses, or the clutter moves with you.

Atlas Bench take

What changed

  1. First published by Atlassian

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

On the Atlassian Cloud roadmap Field schemes See the roadmap item 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 Platform and Migration.

L4

Agents and Automation

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

Atlassian Anthropic
L3

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
L2

Platform and Migration

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

Atlassian Miro AWS Azure
L1

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 you are actually running.

Fixed scope. The assessment reads the estate as it is: instances, schemes, licensing, and the decisions a migration would force you to make anyway. 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