Skip to content
Jira, Rovo, Jira Service Management

Clean up duplicate and unused fields with Jira Admin Agent

Jira Admin Agent, in open beta, finds duplicate and unused fields in Jira Cloud and guides admins through merging or removing them after review. It is coming soon to Atlassian Cloud.

  • Coming soon
  • Low impact

What it is

New feature

Jira admins in the open beta can ask Jira Admin Agent to review fields on their site. It flags fields with matching names or duplicates left by migrations and recommends which one to keep. It also flags unused fields and explains why. The agent shows what each change touches, and nothing happens until an admin approves the plan.

Admins

Admins who opt in under Beta features can start a cleanup from the Fields page or by asking the agent in chat to review duplicate or unused fields, and only their approval triggers any change.

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

Before it lands

  1. Opt in under Beta features in system settings if you want to try it.
  2. Review the impact analysis for each recommendation before approving.

What changed

  1. Added to Atlassian's release notes as coming soon
  2. 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 an agent would inherit.

Fixed scope. The assessment reads the three layers an agent lands on, identity, platform and governance, before anything is switched on. You get the findings, the ownership gaps, and the order to close them in.