Atlassian Rovo Unavailable in Github Copilot

[Hunter Skrasek]

Alright I have followed the instructions here about 20 different times, and no matter what it just does not work. 

https://github.com/marketplace/atlassian

After doing all of the installation steps, when I go to Github Copilot within VS Code it does not recognize `@atlassian-rovo`. It will prompt me to install copilot extensions within VS Code, but nothing shows up when searching for Rovo. 

Am I doing something wrong? I was under the impression the support was already there for Github Copilot to be able to access information about your Jira tickets for example. 

[Jovana Dunisijevic]

Hey @Hunter Skrasek 

Thanks for reaching out! Here are some troubleshooting steps and clarifications:

1. Installation & Permissions

• The Atlassian Rovo Copilot Agent must be installed at the GitHub Organisation level by an Org Admin—not just at the user level. This is a common blocker. Only after the admin installs the Atlassian Rovo - GitHub Marketplace and selects the Atlassian site to connect, will users in the org be able to access Rovo in Copilot

• After installation, users should:

  1. Open VS Code.

  2. Install the GitHub Copilot extension (if not already installed).

  3. Sign in to GitHub in VS Code.

  4. In Copilot chat, type @atlassian-rovo.

  5. You’ll be prompted to authorize access—follow the prompts to authorize both GitHub and Atlassian Rovo, and select your Atlassian site

2. If @atlassian-rovo Doesn’t Appear

• Try this direct authentication link: https://github-copilot-agent.services.atlassian.com/start. This will walk you through selecting your site and authenticating the extension

• Check Copilot Extension Policy: Your GitHub Org admin should verify that Copilot agents are enabled for your org at:
  https://github.com/organizations/<ORGNAME>/settings/copilot/policies

3. What You Should See

• Once set up, you can use @atlassian-rovo in Copilot chat to ask about Jira tickets, Confluence docs, and more—e.g., “What are the issues assigned to me?” or “Show me the acceptance criteria for ABC-123”

• If you still don’t see @atlassian-rovo, double-check that the extension is installed at the org level and that you’re signed in with the correct GitHub account.

4. Known Issues

• Only one Atlassian site can be connected at a time per GitHub org.

• If you see errors like “AI is disabled on xx site through GitHub Copilot in VS Code,” you may need to use /switch <site-name> in Copilot chat to select the correct Atlassian site 5.

• If you’re behind a corporate proxy or have strict network policies, ensure that VS Code can reach the necessary Atlassian and GitHub endpoints.

Let me know how you go!

Kindest regards,

Jov