Unable to use Agent Studio

Question

Here attaching the image where I am not able to select my site in order to open AI Studio in order to start utilizing my Rovo in my JSM Automation, although I am able to see the Rovo agent and Rovo beta in the automation flow and also I had switched to the premium trail plan for this but still not able to figure out what is the problem here I have one POC to complete hence require any help required in order to achieve this connection to work

Sami Shaik · Answer

@Rudresh Singh that dialog is a plain list of the sites in the organisation you are administering, so “No options” means the admin portal does not see a site in this organisation that qualifies, rather than a missing Studio setting. Checked this morning on an organisation where Rovo is active: Atlassian Administration > AI and Rovo > Agents > Manage in Studio opens the same “Select a site” dialog and the dropdown lists the sites. Three things explain an empty list in my experience of how the admin portal is structured, and all three are quick to check.

1. You are in a different organisation from the trial site. A Premium trial started from inside Jira sometimes lands on a site whose organisation is not the one your admin.atlassian.com session has open. Open admin.atlassian.com, use the organisation switcher at the top, and look under Applications for the exact site URL you are running the POC on. If the site is not listed under this organisation, every AI and Rovo page here is looking at the wrong place. The Studio KB says the same in other words: “Confirm you’re on the correct Cloud site where Rovo is enabled.”

2. You are a site or product admin, not an organisation admin. The pages under AI and Rovo are organisation-level. Atlassian’s “Manage who can create in Studio” page says Studio management needs the Studio app admin role, and the Studio access KB says “Only admins can access Rovo Studio”. If someone else created the organisation, ask them to add you as an organisation admin (Settings > Admins) and retry.

3. Staged rollout. The KB also says “Rovo is being rolled out in batches” and recommends logging out and back in or checking again later. That one you cannot fix, but it is worth ruling out the first two before you wait.

Two routes that do not go through that dialog, so you can keep the POC moving:

* Atlassian Administration > Your Applications > Studio > Agents (the path the KB documents), which opens Studio without the site picker.
* @Arkadiusz Wroblewski ’s suggestion, which I would try first: create the agent from Rovo Chat inside the Jira site itself. If that works, the site has Rovo and the problem is isolated to which organisation your admin session is looking at.

One useful signal you already have: “Rovo AI > Use Agent” appearing in the automation action list on that site means Rovo is enabled there. The gap is between the site and the organisation page you are opening, which points back at check 1.

References, read today: Accessing Rovo Studio in Atlassian admin when the Studio menu is missing, Manage who can create in Studio, Manage Rovo access.

Arkadiusz Wroblewski · Answer

Moin

Have you tried creating an agent directly in Rovo Chat? Does the same issue come up there?

Cheers,

Arek🤠🧙‍♂️

Rudresh Singh · Answer

Thank you for reviewing my question.

To provide additional context, I am working on a Jira Service Management POC where the customer has requested an AI-generated executive summary for aging support tickets.

The intended workflow is:

Plain TextJSM Ticket Created       ↓Ticket remains unresolved for more than 1 day       ↓Jira Automation Trigger       ↓Rovo Agent Execution       ↓Analyze ticket activity:   - Summary   - Description   - Public comments   - Internal comments   - Worklogs   - Status transitions   - Assignee changes   - Labels added/removed   - Field modifications       ↓Generate management summary       ↓Post summary back to the Jira ticket as an internal comment

I have already:

* Enabled Rovo access at the organization level
* Enabled beta features
* Confirmed that "Rovo AI → Use Agent" appears in Jira Automation
* Upgraded the environment to a Premium trial
* Verified that the AI and Rovo administration pages are accessible

However, when I navigate to:

Plain TextAdministration→ AI and Rovo→ Agents→ Manage in Studio

the site selection dialog displays "No options", so I cannot create or manage any custom agents.

My questions are:

* Is there any additional configuration required before a Jira Cloud site becomes available in Agent Studio?
* Does the "No options" message indicate a licensing issue, provisioning issue, or missing permission?
* Is there a way to verify whether the site has been onboarded for Rovo Studio and custom agent creation?

Any guidance would be greatly appreciated, as the AI ticket summarization use case is a key requirement for the customer POC.