Skip to content
Jira Service Management, Jira

Field configuration schemes: Field limits for optimized performance

Jira now limits how many fields a field configuration scheme can hold, and rejects updates that would go over the limit in the UI and the public REST API. It has been rolling out to Atlassian Cloud sites since 10 Mar 2026.

  • Rolling out since 10 Mar 2026
  • Medium impact
  • Admin review: api change

What it is

Improvement

When you add a field configuration to a scheme, Jira checks the scheme's total field count. If the change would exceed the limit, Jira rejects it.

Written from Atlassian's release note and checked against it automatically. Atlassian's original stays the source of truth.

Where the rollout is

  1. First published Done
  2. Rollout starts Done

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.

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.