Get started with Jira Admin Agent
Jira Admin Agent is a Rovo agent that helps Jira admins manage fields using natural language. Describe the change you want, and the agent reviews your existing configuration, prepares a plan, and waits for your approval before it applies anything.
Jira Admin Agent is in beta. It supports some configuration changes, not every Jira admin task.
Use Jira Admin Agent to:
Make field changes: Create fields and update field options, field contexts, and field schemes.
Review the impact: See which spaces, work types, boards, filters, and dashboards a change could affect before you apply it.
Handle requests from space admins: Space admins can describe what they need, and the agent creates a request for Jira admins. Set up agent requests
Before you begin
You must be a Jira admin to turn on Jira Admin Agent and make changes with it.
Jira Admin Agent is available on paid Jira plans with Rovo turned on.
Your site must use field schemes. Read more about field schemes
Jira Admin Agent only works with company-managed spaces.
The agent uses your permissions. It can't apply a change that your account can't make in Jira settings.
Turn on Jira Admin Agent
To turn on Jira Admin Agent:
Select Settings in the top navigation bar, then select System.
Select Beta features.
Turn on Jira Admin Agent.
To turn off Jira Admin Agent, follow the same steps and turn off the toggle.
Beta features are turned on for each site separately. To use Jira Admin Agent on another site, turn it on in that site's beta features.
Open Jira Admin Agent
As a Jira admin, you can open Jira Admin Agent from:
The Settings menu: Select Settings in the top navigation bar, then select Ask admin agent.
The Fields page: Select Settings in the top navigation bar, then select Work items > Fields. Select Ask admin agent.
Rovo Chat: Open Chat, then select Jira Admin Agent from the list of agents. Read more about browsing Rovo agents
Space admins in spaces that can send requests can also open the agent from the More actions menu on their space or board.
Make a field change
To make a field change:
Open Jira Admin Agent and describe the change you want. For example, "Add a Customer tier dropdown field to bugs in the Support space."
Review the agent's summary. If it misunderstood, reply with the correction before it builds a plan.
Review the plan. Expand it to see each step and the impact analysis.
Select Apply changes to run all steps, or run individual steps one at a time.
Check that the field configuration works as expected.
Before the agent suggests a new field or option, it checks whether there's an existing one it can reuse. If the agent needs more detail, it asks you.
What the impact analysis shows
The impact analysis lists the spaces, work types, boards, filters, and dashboards that a change could affect. Use it to check the impact before you apply it, especially for fields that more than one space uses.
What Jira Admin Agent can do
In the beta, Jira Admin Agent can make these field changes:
Field options: Add, rename, disable, remove, and restore options in select list, checkbox, and cascading select fields.
Custom fields: Create text, number, date, URL, checkbox, user picker, and single-select and multiple-select fields. Read more about custom fields
Fields in spaces: Add an existing field to a space.
Field contexts: Give a field its own options in a space, set or change a default value, add a space to a context, and rename a context. Read more about field contexts
Field schemes: Create, copy, rename, and delete field schemes, edit their descriptions, and move spaces to a different field scheme.
If the agent can't make a change, it tells you.
Beta limitations
Jira Admin Agent only works with company-managed spaces.
The agent can only make the field changes listed in What Jira Admin Agent can do. Space admins can request other configuration changes, but Jira admins need to complete those changes manually.
Some changes, like creating a field, can take a few minutes. You can leave the agent and come back to review the plan.
Give feedback
Was this helpful?