Jira Admin Agent - Open Beta

Ben Payne

Introducing the Jira Admin Agent Open Beta

https://www.loom.com/embed/fd7c8875f37143bd9983b812ee587c40

Hey Jira Admins 👋

The Jira Admin Agent is now in Open Beta for all paid Jira Cloud plans.

We're building the Admin Agent to help Admins make configuration changes confidently. The aim is to not only save you time, but ensure you can scale your site efficiently.

What can the agent do?

As of today, the agent can perform a subset of field operations and gather configuration requests from your space admins.

Field operations

The supported field operations cover the most common type of admin request and give us a complex enough use case to establish the foundations of how the agent plans, checks impact and makes changes safely. In the Beta, you can ask the agent to:

• Manage field options: add, rename, reorder, disable or enable options (including cascading selects)
• Create a new field
• Add an existing field to a space: the field scheme, screen and layout, in one request
• Create and edit field schemes and associate them with spaces
• Manage field contexts and default values

Every request follows the same flow:

1. Ask in plain language, e.g. "Add a 'Gold' option to the Customer Tier field."
2. Confirm. The agent checks for existing fields or options you can reuse, then confirms it understood your request.
3. Review the plan, including an impact analysis of every space, board, filter and dashboard the change affects.
4. Apply. Nothing changes on your site until you click Apply changes.

Configuration requests from space admins

Space admins often know what they need but don't have the permissions to make the change. With request flow turned on, they can describe what they need to the agent. The agent turns that into a clear, well-formed request and creates it as a work item in a space of your choosing.

Space admins can request any configuration change. During the Beta, you can use the agent to action field-related requests, any other type of request you'll have to handle manually.

To set it up, go to Settings (⚙️) → Ask admin agent → ⚙️. Choose which spaces can send requests, then choose the space and work type where requests should be created.

How to opt in

You'll need to be a site admin, and your site needs to be using the new field schemes.

1. Go to Settings (⚙️) → Beta features.
2. Turn on Jira Admin Agent.

You'll then find the agent under Settings → Ask admin agent, in a space or board's ••• menu, and in Rovo Chat. The agent always works with your own permissions.

A note on the Beta: a typical change takes a few minutes while the agent works through your configuration. We'll keep adding field operations throughout the Beta, and duplicate and unused field cleanup is coming soon.

Help us shape the Admin Agent 💬

We want to build the Admin Agent with you, not just for you. During the Beta, we want to understand where admin work slows you down, which requests take up the most of your time, and what would make the agent part of your day-to-day.

Use the form to tell us what's working and what isn't, give feedback and report issues. Please also fill out our Beta consent form if you want to set up a 1:1 session to talk with the team. Note we'll reach out to as many admins as we can for 1:1 sessions, based on team availability.

👉 Share feedback with the Admin Agent team

Thanks for trying it out. We're looking forward to hearing from you!

Ben Payne, Product Manager, Jira Admin Agent

Marcin Nowak (Radrly)

Great to see the impact analysis step before Apply. That's exactly the part admins usually do by hand, opening every board, filter and dashboard one by one.

Two habits that pair well with the agent, especially once the request flow is on and space admins start asking for fields:

1. Check your field limits before creating new fields. Jira Cloud caps how many fields a space can use, and a handful of "quick" fields from space admin requests adds up faster than people expect. It's worth knowing your headroom before the agent creates one more.
2. Keep a regular look at what actually changed. Approving a plan is one moment, but a few weeks later the useful question is "what changed in our configuration this week, and was it intended?". A short weekly review catches surprises early.

Disclosure: I'm with Radrly, an Atlassian Marketplace partner. We built LimitRadar (https://marketplace.atlassian.com/apps/3501264641) to track and forecast Jira Cloud limits like fields per space, and ConfigRadar (https://marketplace.atlassian.com/apps/142824495) for a weekly view of configuration changes. Both run on Atlassian.

@Ben Payne , a question for the team: will the work items created by the request flow link back to the change the agent applied, so the original request and the approved plan stay together?