> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/automate/connectors/atlassian-rovo.md).

# Atlassian Rovo

Connect Atlassian Rovo to work with Jira and Confluence from Agent Mode

Connect Atlassian Rovo to give Agent Mode access to Jira work and Confluence knowledge, and to turn production findings into assigned, durable follow-up work.

## What You Can Do

**Read and investigate**

> Search Jira for open or past incidents matching this checkout failure, then find the related Confluence runbook and summarize the response steps.
>
> Read the Jira issue for this service degradation and compare its evidence with the latest Confluence architecture notes.

**Take action**

> Create a Jira ticket for this monitor issue. Include the impact, relevant telemetry, investigation link, and acceptance criteria, then assign it to the service owner.
>
> Create or update a Confluence RCA page with the investigation summary, timeline, root cause, evidence, and follow-up actions so the team can learn from it later.

Depending on enabled tools and permissions, Agent Mode can search and read Jira issues and Confluence pages, create and update issues or pages, add comments, and move Jira work through its workflow.

## Setup

1. If your Atlassian organization restricts Rovo MCP access, an Atlassian admin opens **Atlassian Administration → Rovo → Rovo MCP server**, selects **Add domain**, and adds the HTTPS URL pattern for the deployed groundcover host. For example, use `https://app.groundcover.com/**` for the standard groundcover environment. Include the `https://` protocol; Atlassian rejects bare domains.
2. A groundcover workspace admin goes to **Integrations → Connectors → Org Connectors**, selects **Atlassian Rovo**, and enables it.
3. The admin clicks **Connect**, completes OAuth, and reviews the [tool restrictions](/automate/connectors/mcp.md#managing-tool-restrictions).
4. Each user goes to **Integrations → Connectors → My Connections**, selects **Atlassian Rovo**, and clicks **Connect**.
5. Complete the Atlassian OAuth flow and select the Atlassian site to authorize.

{% hint style="info" %}
Agent Mode acts with the connected user's Jira and Confluence permissions, subject to groundcover's tool restrictions. Write actions may require approval.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/automate/connectors/atlassian-rovo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.