Rovo agent dropdown disabled in automation

[Sachin Gupta]

Hi Everyone, 

I created a rovo agent via forge CLI to fetch latest commits from bitbucket ( manifest below .  )  . But when i try to build an automation in jira , i see that "Rovo Agent" dropdown is disabled  and my agent is not available.  i did enable rovo dev in my account as well but not sure how to get around this dropdown issue.   Can someone please guide  ? 

---

App agent  manifest

permissions:

  scopes:

    # This is the correct Workspace scope for Bitbucket, now safe since it's a separate app.

    - read:repository:bitbucket

modules:

  # 1. The Function Module: Links your rovo.js code handler (fetchCommits)

  function:

    - key: fetch-commits-fn

      handler: rovo.fetchCommits

  # 2. The Action Module: Defines the tool's schema for the Rovo Agent

  action:

    - key: fetch-commits-action

      function: fetch-commits-fn

      name: fetchRecentCommits

      description: Fetches all code commits from the Bitbucket 'pitstop' repository within the last 24 hours for incident analysis.

      actionType: custom

  # 3. The Rovo Agent Module: The Agent definition itself

  rovo:agent:

    - key: pitstop-agent

      name: PitStop Commander

      description: An expert incident responder who analyzes code changes.

      prompt: |

        You are a Site Reliability Engineer (SRE) and a specialist in incident response.

        When asked to analyze an incident, you must:

        1. Use the 'fetchRecentCommits' tool to get code changes from the last 24 hours.

        2. Analyze the commit messages and any available diffs for "risky" keywords (e.g., "migration", "database", "timeout", "config change", "deployment").

        3. Summarize the likely root cause and provide a clear, actionable suggestion for immediate next steps.

      actions:

        - fetch-commits-action # References the key of the action module

app:

  runtime:

    name: nodejs22.x

    memoryMB: 256

    architecture: arm64

  # CRITICAL: This ID must match the one Forge gave you for the new app!

[Walter Buggenhout · Accepted solution]

Hi @Sachin Gupta and welcome to the Community!

As the screenshot says, your org admin needs to enable AI on your Atlassian site. This is apparently not the case.

If you are the org admin, this can be done from Admin Settings > Apps > Platform Experiences > AI Settings. If you are not, you will need to reach out to your team's org admin to do this for you.

Hope this helps!

[Sachin Gupta]

Thank you @Walter Buggenhout . I did check the AI settings and both jira and confluence are already enabled .

[Walter Buggenhout]

Yes. And is Rovo enabled on your site? Under the same path I shared before, but on the Rovo page.

[Sachin Gupta]

No. i dont see ROVO page anywhere. when i try rovo from search bar and click on it , i get " We can't find the page you're looking for " .  So it does look like until ROVO is enabled on my site via jira support . 

[Jovana Dunisijevic]

Hey @Sachin Gupta :)

It sounds like Rovo is still not enabled on your cloud site.

Have you tried checking Atlassian apps to see if Rovo is added to the list of apps you have on your cloud site?

For this you definitely need admin access.

Head to Admin settings again (I enter it through User Management option when I click on the setting button next to my avatar on the top right). From there go to Apps > Atlassian apps.

If you happen to have any questions in regards to Rovo Dev, please head to our community space and let us know there how we can help: https://community.atlassian.com/forums/Rovo-Dev/gh-p/rovo-dev-ai-agents

[Sachin Gupta]

I got the update from Atlassian support team that rovo agents are not enabled on personal email address(like gmail one i used) .  Thanks for your help.   Closing this issue