Atlassian integration

Why connect Atlassian?

Product teams accumulate years of context in Jira tickets and Confluence docs that rarely makes it into structured discovery work. Connecting Atlassian means the agent can draw on your actual backlog, past decisions, and team documentation when running playbooks — so every discovery output builds on what your team already knows rather than starting from scratch. The agent accesses your Atlassian data using your own permissions, so it only ever sees what you can see.

What you can do

• Works with Jira issues, epics, and projects
• Works with Confluence pages and spaces
• Semantic search across your entire Atlassian workspace
• Works with Compass services

Related templates

• Map Customer Experience
• Brainstorm Ideas
• Refine Idea
• Spec Idea
• Opportunity

Frequently asked questions

Does this work with Jira Cloud and Jira Data Center?

The integration uses the Atlassian Rovo MCP server, which currently supports Jira Cloud, Confluence Cloud, and Compass. Data Center support depends on Atlassian's MCP roadmap.

What Atlassian data can the agent work with?

The agent works with Jira issues, epics, projects, and comments, as well as Confluence pages and spaces. It uses natural language search to find relevant content across your workspace.

Does the agent work with Jira during a playbook run?

Yes. The agent can draw on Jira issues and backlog context throughout a playbook run — for example, connecting validated opportunities to existing tickets or surfacing related work your team has already done.