Skip to content
Jira

Streamline and manage custom fields options in your site

Jira admins can scan custom fields for unused options and bulk-disable them to stay under a 20,000 option limit per field. It has been generally available on Atlassian Cloud since 20 Oct 2026.

  • Generally available since 20 Oct 2026
  • Medium impact

What it is

Improvement

Jira now has an Optimize tool that finds custom field options not used in any work items or workflows. Admins can disable them in bulk. Once a field reaches 20,000 options, adding new options is blocked until the count drops.

Admins

Admins see new columns for option and context counts on the fields configuration page, and can run Optimize from a field's Actions menu to bulk-disable unused options.

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

What to do now

  1. Review the new option and context count columns on the fields configuration page.
  2. Identify custom fields near or at the 20,000 option limit.
  3. Run Optimize on those fields to find and disable unused options.

Where the rollout is

  1. First published Done
  2. Rollout starts Done
  3. Generally available 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.