> ## Documentation Index
> Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Atlassian

Configure the Atlassian integration to give Resolve AI access to Atlassian data, to use as evidence during the course of investigations.

**Capabilities:**

* Find and follow runbooks stored in your Confluence spaces
* Follow links to runbooks to gather full context
* Triage a ticket
* Add Comments to incident tickets with human-in-the-loop

Check out our [blog](https://resolve.ai/blog/Announcing-Atlassian-MCP-support-for-Resolve-AI) to learn more.

<Info>
  **Prerequisites**: You will need an Atlassian User Account with appropriate permissions to specific Atlassian Apps (such as JIRA, Confluence etc) and to the relevant Spaces / Projects that need to be linked to Resolve AI.
</Info>

## In Resolve AI, add an Atlassian Integration

### 1. Configure the Atlassian Integration

* Log in to [Resolve AI](https://app0.resolve.ai)
* Open [Integrations](https://app0.resolve.ai/integrations) for your organization
* Click the [Atlassian](https://app0.resolve.ai/integrations/mcpAtlassian/connect) integration tile
* Configure the Atlassian MCP endpoint: `https://mcp.atlassian.com/v1/mcp`
* Click **Save**
* A secure browser-based OAuth 2.1 flow is triggered, select the appropriate Applications (JIRA, Confluence) to determine the scope and click **Approve**
* Choose the App site (if applicable) and click **Accept**
* Configure appropriate MCP Tools (View-only are selected by default) and click **Save Configuration**
* After automatic navigation back to the Resolve AI App, click **Save**

### 2. Configure Team Knowledge

Add knowledge to your team's Resolve.md file to help Resolve understand where and how your team's runbooks are organized. This context enables Resolve to efficiently locate relevant runbooks during investigations. Learn more about [Teams & Knowledge](/team-knowledge).

**Resolve.md Configuration Examples:**

**Note:** Add Knowledge to help Resolve understand your Confluence space structure. Here are some examples you can copy and customize with your own space name, page hierarchy, and search strategy.

*Example 1: Centralized runbook location*

```markdown theme={null}
## Where to look for runbooks
This team's runbooks are in the ACME space in Confluence. Runbooks for alerts 
are located under the Runbooks page. Search by alert name or exception message 
from the observability tool to find relevant documentation.
```

*Example 2: Distributed runbook structure*

```markdown theme={null}
## Where to look for runbooks
This team's runbooks are in the ROVER space in Confluence. Focus on the 
"Oncall runbooks" and "Alerts" sections in the tree structure. Runbooks for 
alerts are distributed across these sections. Search by alert name or exception 
message to locate relevant documentation.
```

## Test the Atlassian integration

Chat with Resolve and ask these questions to confirm that the Atlassian integration is working as expected.

1. "What confluence spaces do you have access to?"
2. "What runbooks do you have access to?"
3. "What JIRA projects do you have access to?"
4. "Examine the latest 10 JIRA tickets for project ACME and provide me the pattern of failures"